The detect-note guard reads far enough to see the call - #199
Merged
Merged
Conversation
The guard shipped in #198 sliced 1400 characters from runDetect and looked for the first postJSON in them; the comment added in that same change pushed the call past the slice, so the guard failed on the code it was written for. CI runs no pytest, which is how it merged red. Widened. 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.
Follow-up to #198, which merged with one of its own two source guards failing: it sliced 1400 characters from
runDetectand looked for the firstpostJSONin them, and the comment added in that same change pushed the call past the slice. CI runs no pytest, which is how it merged red. Widened; both guards pass.🤖 Generated with Claude Code