-
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
fix(app,robot-server): Account for failed commands not having a pipetteId #16859
Merged
Merged
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
dde3df0
Refactor: Tighter try/except.
SyntaxColoring 98f0f81
Refactor: Delete redundant assignment.
SyntaxColoring a463c38
Refactor: Delete empty descriptions and redundant Field specifiers.
SyntaxColoring d556364
Refactor: Delete unused None default for placeLabwareState.
SyntaxColoring f846fd0
Refactor: Todo comment for eStopEngaged.
SyntaxColoring 92eea37
Refactor: Links at the end.
SyntaxColoring 3b4dfd1
Expose tip state through the HTTP API.
SyntaxColoring f586fac
refactor(api-client): update types
mjhuff f19c8f9
fix(app): support drop tip during gripper recovery
mjhuff fab4401
Update router tests.
SyntaxColoring File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
@TamarZanzouri Is this a good idea, or does this conflict with any future vision you had for the orchestrator stuff?
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.
DIscussed in-person. I think we're both a little confused about this, but:
RunOrchestratorStore
is largely a glorifiedRunOrchestrator | None
variable. And from that perspective, yes, all of these methods are redundant boilerplate, not offering any abstraction. We can replaceRunOrchestrator.foo()
withRunOrchestrator.run_orchestrator.foo()
without losing anything.There is then a question of, well, why even have
RunOrchestratorStore
. The answer is that other than all of these wrapper methods, it also provides access to a "defaultRunOrchestrator
" for the "stateless command" endpoints, and it gates that access behind there not already being some other, run-controlled,RunOrchestrator
already active. That is a good thing for the server to do, but I wonder if it still makes sense at this layer, now that we have maintenance runs. We might want one higher-level thing mediating between runs, maintenance runs, and stateless commands.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.
Yeah stateless commands are not a thing we use anymore I'm pretty sure - we replaced them with maintenance runs because it turns out we need state for most stuff we want to do.