fix go coverage when parsing blocks out of order#3519
Merged
SpangleLabs merged 2 commits intothought-machine:masterfrom Apr 16, 2026
Merged
fix go coverage when parsing blocks out of order#3519SpangleLabs merged 2 commits intothought-machine:masterfrom
SpangleLabs merged 2 commits intothought-machine:masterfrom
Conversation
goddenrich
changed the title
SpangleLabs
approved these changes
Apr 16, 2026
Contributor
|
This seems to fix some issues we were seeing on the internal repo, and looks good, thank you! |
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
2 participants
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.
previously we were assuming the last block contained the greatest end line. This is not always the case if we parse blocks out of order. Doing so causes plz cover to panic.