-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
JavaScript error #55011
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
Comments
Can you provide the code that caused this error to occur? |
I’m not sure what it is. It’s just continuously piping up on my desktop
…On Thu, Sep 19, 2024 at 8:58 AM Aviv Keller ***@***.***> wrote:
Can you provide the code that caused this error to occur?
—
Reply to this email directly, view it on GitHub
<#55011 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLNMAK5PR3QBV2O7CBEXDILZXLC65AVCNFSM6AAAAABOP267KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHEYTQNBVGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@nodejs/net |
this was fixed in node 20 a few releases ago, without a repro or more info it's impossible to understand |
Duplicate of #51354 Bug was fixed on Node.js 20.12+ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Affected URL(s)
No response
Description of the problem
The text was updated successfully, but these errors were encountered: