Repository navigation
A behavior registry entry that points at no description is found and … - #1333
Merged
Merged
Conversation
…removed 65bba342 had 16 names in the behavior registry with four zero bytes too many, each with an object id shifted by as many (0:68719476736 for 0:16). Every class had its right entry besides, so lookups by name were not affected; the backup, which copies every entry, ended with 'no entry for object at 0:68719476736'. SoilBackupVisitor>>existsAtPinnedVersion: answers false for an id outside its segment, so such an entry is left out of the copy like any other entry without an object. SoilTrackingVisitor shows its trackers the behavior registry with the meta segment (#trackBehaviorRegistry:in:). SoilDatabaseConsistencyTracker reports a name whose id lies outside the meta segment or has no record there as a SoilBrokenRegistryEntry - not as SoilObjectIdOutsideSegment, whose repair would raise the segment index to such an id. Its default repair, SoilRemoveRegistryEntry, takes the name out only while it still points nowhere; the checkpoint of the repair writes the registry, as the journal has no entry for taking a name out. 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.
…removed
65bba342 had 16 names in the behavior registry with four zero bytes too many, each with an object id shifted by as many (0:68719476736 for 0:16). Every class had its right entry besides, so lookups by name were not affected; the backup, which copies every entry, ended with 'no entry for object at 0:68719476736'.
SoilBackupVisitor>>existsAtPinnedVersion: answers false for an id outside its segment, so such an entry is left out of the copy like any other entry without an object.
SoilTrackingVisitor shows its trackers the behavior registry with the meta segment (#trackBehaviorRegistry:in:). SoilDatabaseConsistencyTracker reports a name whose id lies outside the meta segment or has no record there as a SoilBrokenRegistryEntry - not as SoilObjectIdOutsideSegment, whose repair would raise the segment index to such an id. Its default repair, SoilRemoveRegistryEntry, takes the name out only while it still points nowhere; the checkpoint of the repair writes the registry, as the journal has no entry for taking a name out.