fix(app): support drop tip CTAs when two pipettes have tips attached #15984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
In 8.0, drop tip wiz now shows CTAs when a run is successful, and we determine tip attachment status solely from the history of tip attachment commands. Because of this, it's likely users will have protocols similar to the following:
In these situations, we want to prompt users to check tips on both pipettes.
This is simple in theory, but in practice, there are a lot of side-effects we have to consider: run status, whether the run is current, which app is controlling the robot, how to properly load the correct pipette...there's a lot of variables. Unfortunately, drop tip wizard in its current iteration is already overloaded and in need of a refactor. Following the control flow is difficult to say the least. If you're brave, #15947 offers some context behind the most recent systems created.
Test Plan and Hands on Testing
Changelog
Review requests
There is a lot we can do to clean this up, but this entire flow is getting a facelift for 8.1, so I think it's safe to focus on functionality for now.
Risk assessment