-
Notifications
You must be signed in to change notification settings - Fork 186
fix(api): use StateUpdate when mapping legacy module loads #20210
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
Conversation
sfoster1
left a comment
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.
That looks good to me. Are there any remaining command that get mapped without a state update for whatever reason?
mjhuff
left a comment
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.
Ahhh, yeah, this makes sense. Sorry for the hassle, and thank you for fixing!
SyntaxColoring
left a comment
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.
Thank you! One note about requested_model. Otherwise LGTM, assuming the analysis snapshot tests get healed to add the missing entries back into modules.
|
A PR has been opened to address analyses snapshot changes. Please review the changes here: #20215 |
…apshots (#20215) This PR was requested on the PR #20210 Co-authored-by: jbleon95 <[email protected]>
Overview
In RESC-513, a customer reported a magnetic module not appearing on the deck layout or in LPC after updating from robot release 8.5.0 to 8.7.0.
Upon further investigation, the problem was found to be related to the refactor of updating PE state from the command results to
StateUpdatehandling. The change was made in #18639 but the corresponding updates to the legacy command mapper were not made. This has the effect of breaking anything that relies on that module field of the analysis results to be filled, which most obviously are the deck layout and LPC.The fix for this is putting in the legacy command mapper the correct state update, which was already being done for pipette and labware commands.
Test Plan and Hands on Testing
The customer's protocol in the linked ticket was tested, but this minimal reproducible protocol was tested too and now works as expected:
Changelog
set_load_moduleonStateUpdatein legacy command mapper_map_module_loadReview requests
Risk assessment
Low, this only affects OT-2 protocols on versions 2.13 and below and this fix follows the existing pattern we have for pipette and labware loads, which do work on older versions.