-
Notifications
You must be signed in to change notification settings - Fork 179
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
feat(api): Make gripper errors nonfatal #16320
Conversation
This does not seem to handle the case where the gripper drops the labware in transit.
Resolve conflicts in api/src/opentrons/protocol_engine/commands/move_labware.py
# todo(mm, 2024-09-26): This currently raises a lower-level 2015 FailedGripperPickupError. | ||
# Convert this to a higher-level 3001 LabwareDroppedError or 3002 LabwareNotPickedUpError, | ||
# depending on what waypoint we're at, to propagate a more specific error code to users. |
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.
Alternatively, we could consolidate 3001 and 3002.
class Aspirate(BaseCommand[AspirateParams, AspirateResult, ErrorOccurrence]): | ||
class Aspirate(BaseCommand[AspirateParams, AspirateResult, OverpressureError]): |
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.
Unrelated fix, just making sure OverpressureError
shows up in these commands' OpenAPI specs.
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! thank you!
The failing snapshot test is an |
Overview
Closes EXEC-714.
Test Plan and Hands on Testing
Changelog
Catch some exceptions in the gripper part of
MoveLabwareImplementation
and turn them into a new defined error,errorType: "gripperMovement"
.Review requests
See comments below.
Risk assessment
Medium.