Repository navigation
Conversation
Owner
|
Landed via batch PR #6439 (merged) — closing as superseded. |
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
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.
Fixes #6230
Problem
A syntactically valid
nullline causes the archive lookup scanners to dereference a null value. Both session backends stop before later valid archives, and SQLite block restore throws outright.Change
Parse lookup entries as unknown and match identifiers only on non-null objects. The three scanners now continue past unrelated scalar values just as they already do for malformed JSON. Stored archive formats, message/block identities and the restore transaction logic remain unchanged.
Validation
npm run typecheck,npm run build,npm run check:test-import-graphandgit diff --checkpassed on this independent branch.