-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
ERR_INTERNAL_ASSERTION in internalConnectMultiple #48763
Comments
Could you provide any sample code to reproduce? preferably without any dependencies! |
Possibly related to #47644? It might not be a duplicate because #47644 was allegedly fixed (more than once). cc @ShogunPanda |
I can't really do anything without at least a repro code. Will standby this. |
According to @Rand0mF's #47644 (comment), this also happens without using worker threads or web sockets. |
If the bug is related to my changes (which most likely is), it's unrelated to either worker threads or websocket as we're talking about a bug in the connection handling. But I need the exact scenario to reproduce it, unfortunately. |
@hp8wvvvgnj6asjm7 Has the issue been resolved? |
no, but I can't make a small reproducible example and its so random that it's hard to tell what is going on. |
PR-URL: #51045 Fixes: #48763 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
This should have been fixed in #51045. Once it gets in 21.x or 20.x please let me know if you have additional problems. |
PR-URL: #51045 Fixes: #48763 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
This fixes an issue where running individual tests sometimes fails with this error: node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); More info here: nodejs/node#48763 And here: nodejs/node#50383
PR-URL: #51045 Fixes: #48763 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
Version
v20.4.0
Platform
Microsoft Windows NT 10.0.19044.0 x64
Subsystem
No response
What steps will reproduce the bug?
I'm running a worker thread(s) which runs an openWebsocket and passes messages to the main thread via postmessage.
I don't get any messages and after a few minutes, I get this error:
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: