You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2018. It is now read-only.
Beacuse of the way the verb runner is written (that is, synchronously), Do is unable to handle any incoming requests while it's executing a verb sequence.
This may cause problems with Slack connectivity and state when running very long verb sequences.
We should refactor the verb runner to an asynchronous shell execution API, being careful to preserve the waterfall pattern of a sequence's execution.
The text was updated successfully, but these errors were encountered:
Ended up writing a custom promise 'unwrapper' to support creating an array of promises that execute in a waterfall fashion, while still returning the outputs like a map function would, in dc418f3.
Behind the scenes, we're using child_process.exec instead of child_process.spawnSync now.
Beacuse of the way the verb runner is written (that is, synchronously), Do is unable to handle any incoming requests while it's executing a verb sequence.
This may cause problems with Slack connectivity and state when running very long verb sequences.
We should refactor the verb runner to an asynchronous shell execution API, being careful to preserve the waterfall pattern of a sequence's execution.
The text was updated successfully, but these errors were encountered: