Can't send from IRC to Discord afterwards.

[DaVinci030]

I've been using this for more than a year. I'm not good at explaining but here's the issue I copied from the command prompt.

(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) UnhandledPromiseRejectionWarning: TypeError: this.client.listenerCou
nt is not a function
at item.request.gen.end (C:\Users\TV-Nihon\AppData\Roaming\npm\node_modules
discord-irc\node_modules\discord.js\src\client\rest\RequestHandlers\Sequential.j
s:87:29)
at then (C:\Users\TV-Nihon\AppData\Roaming\npm\node_modules\discord-irc\node
_modules\snekfetch\src\index.js:214:21)
at
at process._tickCallback (internal/process/next_tick.js:189:7)
(node:5220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 2)
(node:5220) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead
(node:5220) DeprecationWarning: Collection#find: pass a function instead<

After the "UnhandledPromiseRejectionWarning" shows up, it cannot send transmission from IRC to Discord from one of the multiple channels (while the rest are working).

Screenshots from Discord: https://i.imgur.com/9N6TX6e.png, IRC: https://i.imgur.com/jfaaVTv.png

Can you fix that issue?

P.S. "DeprecationWarning: Collection#find: pass a function instead" annoys me so can you do something about that?

[stonerl]

I do have the exact same problem. Do you need any more debug logging?

[Throne3d]

This looks like it's coming from within discord.js, an upstream library used by discord-irc. I have no idea what it's trying to do there, though, and the bot uses the latest version.

[stonerl]

Thanks for looking into it, let's wait for upstream to fix it. As a workaround, I use a systemd timer to restart discord-irc every hour.

[Kovaelin]

Seems similar to #326 and #328. It looks like there was a fix with another project Headline/Discord-IRC-Relay#13

[zertap]

The error message occurs for me when many lines are sent at once. IRC-> discord cuts off on 5th or so message, iirc.

[Throne3d]

I'll close this issue for now, as I haven't heard anything recent and the above logs look strange (our uses of find are all currently valid?). If you notice any recent connectivity issues, please get back in touch!

[ticpu]

Sorry to say, but I'm still getting that and will probably add --unhandled-rejections=strict to the service to see if systemd can just restart it instead of being blind about the bot not working.

Aug 12 18:49:13 masterpi npm[2731]: (node:2731) UnhandledPromiseRejectionWarning: FetchError: request to https://discordapp.com/api/v7/channels/653307272004632623/messages failed, reason: getaddrinfo EAI_AGAIN discordapp.com
Aug 12 18:49:13 masterpi npm[2731]:     at RequestHandler.execute (/app/node_modules/discord.js/src/rest/RequestHandler.js:107:21)
Aug 12 18:49:13 masterpi npm[2731]:     at runMicrotasks (<anonymous>)
Aug 12 18:49:13 masterpi npm[2731]:     at processTicksAndRejections (internal/process/task_queues.js:93:5)
Aug 12 18:49:13 masterpi npm[2731]: (node:2731) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 32415)

Edit 1: It is very much like #356 too.

Edit 2:
I just wanted to paste my systemd service file in case it might help someone setup a secure instance. RootDirectory obviously has to exist and contain a functional Linux capable of running node/npm for this to work. In my case, it is my actual root BTRFS subvolume. Can't use / there.

[Unit]
Description=Discord to IRC bridge
Wants=network-online.target
After=network-online.target

[Service]
#ExecStart=/usr/bin/npm start -- --config /etc/discord-irc.json
ExecStart=/usr/bin/node --unhandled-rejections=strict dist/index.js --config /etc/discord-irc.json
RootDirectory=/mnt/btrfs/@root
BindReadOnlyPaths=/usr/src/discord-irc:/app
BindReadOnlyPaths=/home/alarm/.config/discord-irc/config.json:/etc/discord-irc.json
BindReadOnlyPaths=/run/systemd/resolve/resolv.conf:/etc/resolv.conf
SystemCallFilter=@system-service
SystemCallFilter=~@chown @resources @setuid setns
PrivateDevices=true
ProtectHome=tmpfs
WorkingDirectory=/app
DynamicUser=true
Restart=always
RestartSec=15
Environment=HOME=/home

[Install]
WantedBy=multi-user.target

[Throne3d]

Hrrm, that's a shame. Are you testing out the latest alpha version (v2.9.0-alpha)? If not, would you be able to try that out and see if the same issue occurs? This seems to be happening in discord.js, which is a library we rely on, but it's had quite a significant recent update, and I wonder if it might have improved the behavior around this.

[ticpu]

It is running v2.8.1-11-g5af02c1 at the moment, is it considered 2.9 or should I git pull?

[Throne3d]

I can't actually seem to find g5af02c1 in the repo (is that a Git commit?), so I'm not sure if you're on a more recent version than the release, but 2.8.1 was 41f8444, and the main relevant change for 2.9.0-alpha happened in f047ce0 - at the end of the v2.8.1...v2.9.0-alpha comparison. I'd git pull to be safe!

[ticpu]

My bad, I should have git log before posting. g5af02c1 = git shorthash when you remove the leading g. Git log shows that this short hash is "Add 2.9.0-alpha to CHANGELOG" 5af02c1