PSA: If you're on node `20.0.0` and above, and want to use this library with `client.configuration.connection.secure === true`, use the argument `--no-network-family-autoselection`

[brian6932]

Connecting over ws is unaffected
This is relatively rare now, but eventually, you'll get the following error:

node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^
NotSpecified: (:) [], RemoteException
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
NotSpecified: (:) [], RemoteException
    at new NodeError (node:internal/errors:399:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1107:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}
NotSpecified: (:) [], RemoteException
Node.js v20.2.0

[brian6932]

Ok, I've looked into this issue a bit more, and it seems to only occur when

client.configuration.connection.secure === true && client.configuration.connection.method === `tcp`

If you make a very smol connection to tmi over tcp:

import { connect } from 'net'

const xd = connect(6667, `irc.chat.twitch.tv`, () => console.log(`connected`))

xd
	.setEncoding(`utf8`)
	.setNoDelay()
	.on(`connect`, () => xd.write(`nick justinfan123\njoin #tmiloadtesting2\n`))
	.on(`data`, _ => console.log(_))

It doesn't exhibit the issue either

Oddly enough, doing the same thing securely is working fine for me

import { TLSSocket } from 'tls'

const xd = new TLSSocket()
	.connect(6697, `irc.chat.twitch.tv`, () => console.log(`connected`))

xd
	.setEncoding(`utf8`)
	.setNoDelay()
	.on(`connect`, () => xd.write(`nick justinfan123\njoin #tmiloadtesting2\n`))
	.on(`data`, _ => console.log(_))

[tniessen]

@brian6932 To clarify, does 20.3.0 still result in the same ERR_INTERNAL_ASSERTION error, or in a different error? Could you post the stack trace (including the Node.js version at the bottom) for Node.js 20.3.0, please?

[brian6932]

yes

node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^
NotSpecified: (:) [], RemoteException
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
NotSpecified: (:) [], RemoteException
    at new NodeError (node:internal/errors:405:5)
    at assert (node:internal/assert:14:11)
    at internalConnectMultiple (node:net:1106:3)
    at Timeout.internalConnectMultipleTimeout (node:net:1644:3)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}
NotSpecified: (:) [], RemoteException
Node.js v20.3.0

[ShogunPanda]

@brian6932 I cannot reproduce this on Node.js 20.3.0.
Can you please post the result of dig irc.chat.twitch.tv here?

[brian6932]

; <<>> DiG 9.16.41 <<>> irc.chat.twitch.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57154
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;irc.chat.twitch.tv.		IN	A

;; ANSWER SECTION:
irc.chat.twitch.tv.	148	IN	A	44.227.173.36
irc.chat.twitch.tv.	148	IN	A	34.212.92.60
irc.chat.twitch.tv.	148	IN	A	44.237.40.50

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 13 10:09:54 Eastern Daylight Time 2023
;; MSG SIZE  rcvd: 138

[ShogunPanda]

Ok, another question: can you please provide the entire file (or a meaningful repro) that you're trying to execute?

[brian6932]

@ShogunPanda https://github.com/pajlada/brian-test-repro You can use this

Ok, I've looked into this issue a bit more, and it seems to only occur when

client.configuration.connection.secure === true && client.configuration.connection.method === `tcp`

As explained here, if secure is true (default), and tcp is the method (default), it will produce the error

[pajlada]

A more minimal example

// index.mjs
import { Socket } from "net";
import { TLSSocket } from "tls";

const port = 6697;
const host = "irc.chat.twitch.tv";

const backingSocket = new Socket();
const stream = new TLSSocket(backingSocket);

backingSocket.connect(port, host);
stream.connect(port, host);

then node index.mjs - no library dependencies needed

Host and port can be changed too and it still happens. I tested with port set to 443 and host set to httpbin.org

And confirmed it works with node --no-network-family-autoselection index.mjs

[ShogunPanda]

Hello!
I was able to reproduce this and I have a PR coming soon for node. It will probably be included in 20.4.0 and 18.17.0.

[ShogunPanda]

Hello. The fix for this is in the PR above.
I'll let you know once it lands so you can try a nightly build to see if it solves your issue.