-
Notifications
You must be signed in to change notification settings - Fork 30k
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
undici leaking Symbol to global space in 18.2 (but not 18.1) #43157
Comments
I think it is true that the It is added #43059 https://github.com/nodejs/undici/blob/d023b2d808169b7269307d2546125b780e7be5ad/lib/global.js#L5-L27 |
Aren't we supposed to detect leaked globals in the Node.js CI? |
We probably only test for actual globals and not global symbols. Does V8 even provide an API to get a list of global/shared symbols (created via |
The check is in Lines 266 to 368 in 26846a0
|
We currently only test for enumerable globals, for some reason. I've #42056 open that should address this, but it's still blocked on nodejs/build#2879. |
As the I'll go ahead and close this but please reopen if needed. |
Version
18.2.0
Platform
macOS 20.6.0
Subsystem
http
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
I'll try to come up with a narrower test case later (unless someone finds the issue before then), but running tests for https://github.com/Trott/solr-proxy in 18.2.0 results in a report that
Symbol(undici.globalDispatcher.1)
is leaked. Running the same test with Node.js 18.1.0 does not report that.Refs: https://github.com/Trott/solr-proxy/runs/6525176564?check_suite_focus=true
Additional information
No response
The text was updated successfully, but these errors were encountered: