Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SequentialHandler.runRequest throws a TimeoutOverflowWarning

See original GitHub issue

Which package is this bug report for?

rest

Issue description

Discord.JS seems to throw a TimeoutOverflowWarning whenever calling REST.request directly.

Node version: 16.17.0 Version: @discordjs/rest @1.3.0

(node:28) TimeoutOverflowWarning: 18446744073709548000 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
    at new Timeout (node:internal/timers:171:15)
    at node:timers/promises:81:21
    at new Promise (<anonymous>)
    at Object.setTimeout (node:timers/promises:80:15)
    at SequentialHandler.runRequest (/app/node_modules/@discordjs/rest/dist/lib/handlers/SequentialHandler.cjs:128:26)
    at async SequentialHandler.queueRequest (/app/node_modules/@discordjs/rest/dist/lib/handlers/SequentialHandler.cjs:99:14)
    at async REST.request (/app/node_modules/@discordjs/rest/dist/lib/REST.cjs:52:22) <-- we call this
    at async sendDirectMessage (/app/src/utils/discordRestExtensions.js:6:21)
    at async ReminderService.pollForReminders (/app/src/services/reminderService.js:50:11)

Code sample

No response

Package version

@discordjs/rest @1.3.0

Node.js version

16.17.0

Operating system

Ubuntu

Priority this issue should have

Medium (should be fixed soon)

Which partials do you have configured?

Not applicable (subpackage bug)

Which gateway intents are you subscribing to?

Not applicable (subpackage bug)

I have tested this issue on a development release

No response

Issue Analytics

State:
Created 10 months ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

Jiralitecommented, Nov 10, 2022

Turns out this is indeed a Discord issue. I’ll be closing this as there’s nothing we can do library-side. Feel free to join the above server & thread for updates. In addition, the new implementation was disabled, so restart (if applicable):^1

1reaction

squirrelboyecommented, Nov 10, 2022

This is a high/critical priority issue IMO. Not sure what is causing it, but when it happens it spams my console with this error, logging the error at a rate of 4 GB per minute and shoots my instance CPU usage up 5x. It continues to spam until the bot is restarted.

This first started last night around 8pm ET. I restarted the bot and it has been fine until about an hour ago when the issue started once again.