forked from anomalyco/opencode
-
Notifications
You must be signed in to change notification settings - Fork 0
audit(F4): narrow SSE_STALL_MESSAGE_RE to the emitted format #7
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
Closed
+48
−5
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
/^...$/in JS will also match before a final trailing newline, so this can still accept"SSE read timed out after 120000ms\n", which isn’t the emitted wrapSSE() format. If the goal is truly exact-format matching, either add a trailing negative lookahead to reject\r?\nor switch to a non-regex check that enforces both the prefix and digit+"ms" suffix without$’s newline behavior.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.
Thanks for the careful review — applied fixes for comments 1 and 3.
Respectfully pushing back on this one with empirical evidence: in V8/Bun (and ECMAScript generally, without the
mflag),$is true end-of-string and does NOT match before a trailing\n. Verified in Bun 1.3.13:The "$ matches before final \n" behavior is Python/Ruby semantics, not JS (in JS you'd need the
mflag, which we don't set).That said, the concern is legitimate in spirit, so I added the trailing-newline case explicitly to the regression test suite at
message-v2-sse-stall.test.ts:99and documented this behavior in a code comment. If the regex engine semantics ever change, we'll know.