-
Notifications
You must be signed in to change notification settings - Fork 5k
process: don't hand an empty JSValue to reifyStaticProperty on builder exception #34879
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
robobun
wants to merge
1
commit into
main
from
farm/f681d3ac/process-lazy-builder-exception-handling
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.
🟣 Pre-existing (not introduced by this PR), but visible in the touched hunk: lines 2528-2529 both
putDirectthe key"excludeEnv"— the second, whose value is"SIGUSR2", was almost certainly meant to be"signal". As-is,process.report.signalisundefinedandprocess.report.excludeEnvis the string"SIGUSR2"instead of booleanfalse. Worth fixing while you're in this function, but shouldn't block the PR.Extended reasoning...
What the bug is
In
constructProcessReportObject(BunProcess.cpp:2528-2529), two consecutiveputDirectcalls use the identical key"excludeEnv":The second call overwrites the first. Node's
process.reportexposes asignalproperty that defaults to'SIGUSR2'and anexcludeEnvboolean that defaults tofalse, so the second line's key was clearly meant to be"signal"— this is a copy-paste slip.Step-by-step
process.report→ the lazyPropertyCallbackconstructProcessReportObjectruns.report.excludeEnv = false.report.excludeEnv = "SIGUSR2", overwriting step 2.report.signal.process.report.excludeEnv === "SIGUSR2"(string, wrong type) andprocess.report.signal === undefined(missing).Why nothing prevents it
putDirecton an existing own property silently replaces the slot; it doesn't warn or throw on duplicate keys. There is no test asserting the type ofprocess.report.excludeEnvor the presence ofprocess.report.signal— the existingprocess.reporttest just callsJSON.stringify(process.report.getReport()), and this PR's new test only checkstypeof process.report === "object".Impact
Node-compat divergence on
process.report: code that readsprocess.report.signal(e.g., to know which signal triggers report generation) getsundefined, and code that branches on the booleanprocess.report.excludeEnvsees a truthy string instead offalse. Low practical impact sinceprocess.reportis largely a stub in Bun, but it's a straightforward correctness bug.Fix
Change the second key to
"signal":Relation to this PR
These lines are unchanged context in the diff —
git blameattributes them to a commit predating this PR. This PR only replaced theRETURN_IF_EXCEPTION(scope, {})on the line immediately below with the newclearAndReportLazyPropertyExceptionhelper. The bug is unrelated to the exception-handling change; it's flagged only because it sits inside the touched hunk and is trivial to fix while here.