-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
FATAL ERROR when setting 'onread' of a socket #37369
Comments
There are 3
Of these only the attribute with value |
We can't really consider this to be a bug. The example is monkey patching an internal function in a way that is simply not supported. The internal symbols (in this case the hidden What is the use case you're trying to achieve? It's possible we need an alternative public API to support the case. |
Hi James, I'm sorry this wasn't clear - the bug isn't that The use-case is that in some cases, eg. the algorithm used by "clone" NPM package, assignment can be performed on objects without knowing whether the object is considered internal or non-internal. Arguably any objects exposed to JavaScript should behave legally to JavaScript operations performed on them. |
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
A Type Error should be thrown.
What do you see instead?
Additional information
Alternative POC:
Unexpectedly also crashes when assigning to a newly created object, sharing the 0th, 1st, or 2nd prototype.
Alternative error:
The following issues are related:
The text was updated successfully, but these errors were encountered: