A detect clears the last attempt's note, and says which 503 it was - #198
Merged
Merged
Conversation
… 503 it was "Automatic detection is unavailable on this rig" — under a detect that was, at that moment, succeeding with four embryos. The note was from a press made in the half-minute between the page connecting (00:31:18) and the device layer attaching (00:31:50): the route answered 503 "Microscope not connected" before reaching the microscope, the pane wrote its one sentence for any 503, and nothing ever cleared it when the next detect started. Two changes. A detect clears the note before it starts. And the two 503s are told apart: "not connected" is a wait — the rig is still coming up — while a device layer with no SAM is this rig's shape and will not change by waiting. They were one sentence, and it was the wrong one for the case people actually hit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A stale message, not a failed detection. The device-layer log shows the detect at 00:32:05 succeeding — four embryos, HTTP 200. The note came from an earlier press made in the half-minute between the page connecting (00:31:18) and the device layer attaching (00:31:50): the web route answered
503 Microscope not connectedbefore ever reaching the microscope, the pane wrote its one sentence for any 503, and nothing cleared it when the next detect started — so it sat under the succeeding run.Two source guards in
tests/test_acquisition_configurator.py.🤖 Generated with Claude Code