-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(api): return stall/collision defined error from stacker store #17613
chore(api): return stall/collision defined error from stacker store #17613
Conversation
…fined error returned
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a note on the error docstring.
Co-authored-by: Alise Au <20424172+ahiuchingau@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should add a new error code for this, yeah. Especially since the axis names overlap with the flex axes (both have X
), and double especially since we're putting it in a different DefinedError
kind. And yeah, when we build an error instance we'll want to fill in the axis and serial details.
Also, IMO this is more "flex stacker" than it is "stall error", so let's put the definition of the defined error in a new flex_stacker/common.py
file in the engine, since nothing outside of a flex stacker command will ever want to build one.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #17613 +/- ##
==========================================
- Coverage 25.70% 24.56% -1.15%
==========================================
Files 2843 2848 +5
Lines 218884 219240 +356
Branches 17947 18075 +128
==========================================
- Hits 56268 53855 -2413
- Misses 162601 165376 +2775
+ Partials 15 9 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple details, looks good other than those once tested
Co-authored-by: Seth Foster <seth@opentrons.com>
Co-authored-by: Seth Foster <seth@opentrons.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good once we fix the testing and remove the import from shared-data
!
tested and works as expected! |
Overview
closes https://opentrons.atlassian.net/browse/EXEC-1198.
return a defined error from store and retrive when encountering a stall.
Test Plan and Hands on Testing
upload a protocol to the flex and trigger a stall upon store + retrive.
make sure the server is returning a defined error and not propagating the stall collision error.
*** will add a protocol soon and will test locally as well
Changelog
retreive
andstore
now catch aFlexStackerStallError
and return a defined error for ER.FlexStackerStallOrCollisionError
to the defined errors union.Review requests
axis
andserial
as props to the error?Risk assessment
low. return a defined error instead of the error propagating.