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.
fix: restore message snapshot when tagging fails mid-pass #142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix: restore message snapshot when tagging fails mid-pass #142
Changes from all commits
ef0f13bFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
structuredClonefailure propagates outside the tagging try-catchsnapshotMessagesForTaggingis called one line before thetryblock that catches tagging errors. If any message part contains a non-cloneable value (e.g., aPromise, a class instance with methods, or a circular reference),structuredClonethrows aDataCloneError. Because the call is outside the try-catch, that error would propagate unhandled from the transform — a harder failure than the tagging error this PR is meant to handle gracefully. The code comment says "Parts are JSON-like OpenCode payloads", so this is theoretical for normal operation, but moving the snapshot inside the try-catch (or wrapping it in its own try-catch that falls back to a no-op restore) would eliminate the exposure.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
splicecan hit V8's argument-count limitmessages.splice(0, messages.length, ...preTagSnapshot)passes every element ofpreTagSnapshotas a separate argument tosplice. V8 (and most JS engines) cap the number of arguments per call at ~65 536; exceeding it throws aRangeError: Maximum call stack size exceeded. In practice the message window is small, but a loop-based alternative achieves the same in-place mutation without the argument-count constraint.