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

fix(app): Fix improper transitioning run status in protocol runs #14454

Closed

Conversation

mjhuff
Copy link
Contributor

@mjhuff mjhuff commented Feb 8, 2024

Closes RQA-2291, RQA-2307, RQA-2306, RQA-2304

Overview

This PR fixes a bug on the app side in which the incorrect property React Query was used. In order to prevent any refetches, staleTime is the correct choice. Certain useRunQuery and useAllRunQuery hooks that were not updating properly now update as expected. Also, the removed RUN_STATUS_STOP_REQUESTED is added back to useRunStatus(), since its removal was causing bug RQA-2306.

The python side changes are all sanity check changes - nothing new here. A new push is added to the remove method, since we want to push on every new CRUD. I don't know if this was causing bugs, but it should be fixed.

Test Plan

  • Run through the bug tickets and make sure they now work.

Changelog

  • Fixed modals/buttons not updating correctly related to protocol runs.

Risk assessment

low

github-actions bot and others added 7 commits February 7, 2024 09:49
addition of ignoreTipConfiguration flags
…ropriately

Instead of checking the refetchInterval property to see if a notification refetch should occur, we
should check if staleTime is infinity. This accurately captures the refetchHTTP behavior that we
actually want.
@mjhuff mjhuff requested review from CaseyBatten and a team February 8, 2024 19:11
@mjhuff mjhuff requested review from a team as code owners February 8, 2024 19:11
@mjhuff mjhuff requested review from b-cooper and shlokamin and removed request for a team and b-cooper February 8, 2024 19:11
Copy link

codecov bot commented Feb 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5fffd3e) 68.15% compared to head (91520f5) 68.15%.
Report is 14 commits behind head on edge.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #14454      +/-   ##
==========================================
- Coverage   68.15%   68.15%   -0.01%     
==========================================
  Files        1628     1628              
  Lines       54954    54952       -2     
  Branches     4141     4140       -1     
==========================================
- Hits        37452    37450       -2     
+ Misses      16814    16813       -1     
- Partials      688      689       +1     
Flag Coverage Δ
app 33.87% <ø> (-0.02%) ⬇️
react-api-client 66.16% <ø> (ø)

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

Files Coverage Δ
api/src/opentrons/hardware_control/types.py 96.55% <ø> (ø)
...c/opentrons/protocol_engine/clients/sync_client.py 100.00% <ø> (ø)
...rc/opentrons/protocol_engine/execution/movement.py 100.00% <ø> (ø)
api/src/opentrons/protocol_engine/state/motion.py 100.00% <ø> (ø)
react-api-client/src/runs/useAllRunsQuery.ts 91.66% <ø> (ø)
robot-server/robot_server/runs/run_store.py 100.00% <ø> (ø)

... and 2 files with indirect coverage changes

@mjhuff mjhuff changed the base branch from edge to chore_release-7.2.0 February 8, 2024 20:20
@mjhuff mjhuff requested a review from a team as a code owner February 8, 2024 20:20
@mjhuff mjhuff closed this Feb 8, 2024
@mjhuff
Copy link
Contributor Author

mjhuff commented Feb 8, 2024

Will reopen with correct branch targeted.

@mjhuff mjhuff deleted the app_fix-notificiation-protocol-runs branch February 8, 2024 20:29
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.

1 participant