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
Tip length and pipette offset calibrations are intended to be fetched in the app when a redux action of type SESSION_DELETE_SUCCESS hits the stream. The epics that implement this (in app/src/calibration/pipette-offset and app/src/calibration/tip-length) trigger properly and emit an action with the proper action type, but the action payload - which includes things like the robot name to actually query - is malformed, so the endpoints never actually get hit.
Also, those epics should probably trigger on the DELETE_SESSION action, because the various flows that do calibration actually clear their modals then and render a spinner on the button that triggers them while the delete proceeds. If we continue to trigger the refetch on DELETE_SESSION_SUCCESS, until the delete ends (and the delete incurs some robot motion so it could be a while) we won't see updated data.
Let's fix both these issues.
The text was updated successfully, but these errors were encountered:
The epics to fetch pipette offset calibration and tip length calibration
were using the wrong rxjs operators to emit their actions, and
consequently would fire at the right times but not actually incur a
fetch from the robot.
Closes#6747
The epics to fetch pipette offset calibration and tip length calibration
were using the wrong rxjs operators to emit their actions, and
consequently would fire at the right times but not actually incur a
fetch from the robot.
In addition, the UI works much better if the data is fetched when the
session delete _starts_ rather than completes successfully, since most
session wizards go away when the delete begins and therefore let the
user see the places where the data goes.
Closes#6747
Co-authored-by: ahiuchingau <[email protected]>
Tip length and pipette offset calibrations are intended to be fetched in the app when a redux action of type SESSION_DELETE_SUCCESS hits the stream. The epics that implement this (in
app/src/calibration/pipette-offset
andapp/src/calibration/tip-length
) trigger properly and emit an action with the proper action type, but the action payload - which includes things like the robot name to actually query - is malformed, so the endpoints never actually get hit.Also, those epics should probably trigger on the DELETE_SESSION action, because the various flows that do calibration actually clear their modals then and render a spinner on the button that triggers them while the delete proceeds. If we continue to trigger the refetch on DELETE_SESSION_SUCCESS, until the delete ends (and the delete incurs some robot motion so it could be a while) we won't see updated data.
Let's fix both these issues.
The text was updated successfully, but these errors were encountered: