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
There are some commands that get issued in sequence without UI changes or user interaction. Each command is only valid when the server in the appropriate state, and so should be triggered when the results from the previous command arrive at the app; refactor these chained commands away from their current sleep()-based ordering into a proper epic.
The text was updated successfully, but these errors were encountered:
In order to avoid various race conditions created by sequential commands being requested of the
robot during/before/after calibration sessions, create mechanism to ensure that they are dispatched
sequentially. Also ensure that wizard only closes on successful deletion, to avoid orphaned session.
Closes#6535
In order to avoid various race conditions created by sequential commands being requested of the
robot during/before/after calibration sessions, create mechanism to ensure that they are dispatched
sequentially. Also ensure that wizard only closes on successful deletion, to avoid orphaned session.
Closes#6535
There are some commands that get issued in sequence without UI changes or user interaction. Each command is only valid when the server in the appropriate state, and so should be triggered when the results from the previous command arrive at the app; refactor these chained commands away from their current sleep()-based ordering into a proper epic.
The text was updated successfully, but these errors were encountered: