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 Oct 1, 2022. It is now read-only.
When putting a plan on the RunEngine queue, it would be helpful to zip its callbacks along with the plan, rather than depend solely on Teleporter. When the forever_plan gets the next plan off the queue, it could also get the associated callbacks, and transiently add them to the RunEngine.
In this way, an interface could throw many plans at the RunEngine, and dispatch the document stream to the appropriate channels.
The text was updated successfully, but these errors were encountered:
When putting a plan on the RunEngine queue, it would be helpful to zip its callbacks along with the plan, rather than depend solely on Teleporter. When the forever_plan gets the next plan off the queue, it could also get the associated callbacks, and transiently add them to the RunEngine.
In this way, an interface could throw many plans at the RunEngine, and dispatch the document stream to the appropriate channels.
The text was updated successfully, but these errors were encountered: