Skip to content
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

refactor(app): verify probe presence before pipette calibration and labware position check #14126

Merged
merged 7 commits into from
Dec 7, 2023

Conversation

ahiuchingau
Copy link
Contributor

Overview

The app now checks for probe presence for pipette before performing pipette calibration and labware position check.

@ahiuchingau ahiuchingau requested review from a team as code owners December 6, 2023 23:04
@ahiuchingau ahiuchingau requested review from smb2268 and removed request for a team December 6, 2023 23:04
Copy link

codecov bot commented Dec 6, 2023

Codecov Report

Merging #14126 (08fd033) into chore_release-7.1.0 (390d022) will increase coverage by 0.02%.
Report is 17 commits behind head on chore_release-7.1.0.
The diff coverage is 14.70%.

Additional details and impacted files

Impacted file tree graph

@@                   Coverage Diff                   @@
##           chore_release-7.1.0   #14126      +/-   ##
=======================================================
+ Coverage                70.44%   70.46%   +0.02%     
=======================================================
  Files                     2483     2512      +29     
  Lines                    70328    71198     +870     
  Branches                  8770     8963     +193     
=======================================================
+ Hits                     49542    50172     +630     
- Misses                   18635    18837     +202     
- Partials                  2151     2189      +38     
Flag Coverage Δ
app 67.66% <14.70%> (-0.01%) ⬇️
protocol-designer 44.99% <ø> (+<0.01%) ⬆️
shared-data 75.02% <ø> (-0.84%) ⬇️
step-generation 86.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
.../organisms/PipetteWizardFlows/ProbeNotAttached.tsx 21.42% <0.00%> (ø)
...p/src/organisms/PipetteWizardFlows/AttachProbe.tsx 72.00% <71.42%> (+2.35%) ⬆️
...src/organisms/LabwarePositionCheck/AttachProbe.tsx 5.55% <0.00%> (+0.90%) ⬆️
...pp/src/organisms/ModuleWizardFlows/AttachProbe.tsx 5.55% <0.00%> (-1.12%) ⬇️

... and 33 files with indirect coverage changes

mount: mount,
},
},
]
setIsPending(true)
refetch()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this refetch in so that we would have the most up to date attachedInstrument state to check for the tip. Is that still necessary? Looks like it could be removed.

The nesting of the promises was on purpose to get the right error screen
to display so reintroduce it, but it works slightly differently now
because we also don't need the instruments query anymore since we were
just using that to get the tip status.

Also add the failure screen to the module calibration
@sfoster1
Copy link
Member

sfoster1 commented Dec 7, 2023

The nesting definitely ended up being needed but @smb2268 you're right the instruments query was not, so ditched that. Tested on a robot.

Copy link
Contributor

@smb2268 smb2268 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good to me! Thanks for updating 🚀

@sfoster1 sfoster1 merged commit 7e765eb into chore_release-7.1.0 Dec 7, 2023
42 of 45 checks passed
@sfoster1 sfoster1 deleted the app_verify-probe-presence branch December 7, 2023 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants