Josh Wulf

These tests still fail with the pure JS implementation in zeebe-node 2.4.0 with Zeebe 1.2.1

To mitigate this - because an end-user putting a catch-all on uncaught process exceptions is not ideal - finding out how to attach an onError handler to that TLSSocket is...

@grexe does this do what you are looking for? https://github.com/StephenOTT/Workflow-Linter

What would make this next-level is the ability to validate the tasks against the schema, so that I could be told in the modeller: "_Task of type `email:send` is missing...

Here is a linter service that does validation based on user-defined rules: https://github.com/StephenOTT/Workflow-Linter

Cmd + Steps to reproduce: * Create a new model. * Click Start event. * Add Task. * Add End Event to Task. * Press Cmd + twice. Model disappears

[Capto_Capture 2020-12-16_01-39-32_PM.mp4.zip](https://github.com/zeebe-io/zeebe-modeler/files/5699539/Capto_Capture.2020-12-16_01-39-32_PM.mp4.zip)

Is this addressed by https://github.com/ziyasal/vscode-open-in-github/commit/32ae2700e5bd80df58942e97211bf649ea13d9cd?

Looks like this is in https://github.com/ziyasal/vscode-open-in-github/commit/32ae2700e5bd80df58942e97211bf649ea13d9cd

The easy and obvious one is `t = 2 * t`. So, 1s, 2s, 4s, 8s, 16s, 32s, 64s ... Maybe with a maximum bound? This is how I do...