Skip to content

refactor(api): Flesh out developer documentation for unsafe commands#18151

Merged
SyntaxColoring merged 2 commits into
edgefrom
flesh_out_unsafe
Apr 23, 2025
Merged

refactor(api): Flesh out developer documentation for unsafe commands#18151
SyntaxColoring merged 2 commits into
edgefrom
flesh_out_unsafe

Conversation

@SyntaxColoring
Copy link
Copy Markdown
Contributor

Overview

Edit a docstring to elaborate on the meaning of "unsafe" Protocol Engine commands, following an in-person discussion with @sfoster1 and @ahiuchingau.

Changelog

  • Flesh out the opentrons.protocol_engine.commands.unsafe module docstring.
  • Fix an unrelated copy-paste error in a comment in robot-server's migrations.

Review requests

  • Is this clearer? Anything else to add?

  • This part is something that I'm adding on-the-fly. We haven't discussed it. Does this seem like a good expectation?

    Because we don't expect unsafe commands to be used in any protocols whose behavior we must preserve, we may change the commands' semantics over time. We may also change their shapes if we're confident that it won't break something in robot-server's persistent storage.

Risk assessment

No risk.

Copy link
Copy Markdown
Contributor

@TamarZanzouri TamarZanzouri left a comment

Choose a reason for hiding this comment

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

thank you for doing this!

therefore never be used in protocols, and should only be used otherwise as a last
resort.

These exist as a necessary evil for implementing things like error recovery.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

hahaha love it

@SyntaxColoring SyntaxColoring merged commit 2376fd1 into edge Apr 23, 2025
31 checks passed
@SyntaxColoring SyntaxColoring deleted the flesh_out_unsafe branch April 23, 2025 18:57
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 17, 2025
ddcc4 pushed a commit that referenced this pull request May 19, 2025
ddcc4 pushed a commit that referenced this pull request May 19, 2025
ddcc4 pushed a commit that referenced this pull request May 19, 2025
ddcc4 pushed a commit that referenced this pull request May 20, 2025
ddcc4 pushed a commit that referenced this pull request May 20, 2025
ddcc4 pushed a commit that referenced this pull request May 22, 2025
ddcc4 pushed a commit that referenced this pull request May 23, 2025
ddcc4 pushed a commit that referenced this pull request May 24, 2025
ddcc4 pushed a commit that referenced this pull request May 24, 2025
ddcc4 pushed a commit that referenced this pull request May 29, 2025
ddcc4 pushed a commit that referenced this pull request May 29, 2025
ddcc4 pushed a commit that referenced this pull request May 29, 2025
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.

3 participants