Repository navigation
A previous version that runs into the record after it is a broken chain - #1329
Merged
Merged
Conversation
A link into the middle of a record reads user bytes as a head. In the accounts database such a head (version 53, behind 187082) passed the order check and its descriptions came out as 19 missing behavior descriptions instead of one broken version chain. A record is written behind the ones before it, so a previous version whose end lies beyond the start of the record that points to it cannot be one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ccessor A previous version behind the record that points to it is the order check's to name; the overlap guard had answered for it first. Co-Authored-By: Claude Opus 5.5 <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 link into the middle of a record reads user bytes as a head. In the accounts database such a head (version 53, behind 187082) passed the order check and its descriptions came out as 19 missing behavior descriptions instead of one broken version chain. A record is written behind the ones before it, so a previous version whose end lies beyond the start of the record that points to it cannot be one.