revolt.js throws exception when uncached user leaves a server #8

Closed
opened 2026-02-16 12:26:44 -05:00 by yindo · 0 comments
Owner

Originally created by @sussycatgirl on GitHub (Dec 11, 2021).

Originally assigned to: @sussycatgirl on GitHub.

It appears that when a user leaves a server (or gets kicked/banned) and is not already cached, revolt.js attempts to fetch that user. If it is unable to fetch it (Usually because of missing permission), an exception is thrown.

This is not a big issue in browser applications, but it almost certainly causes node.js applications such as bots to exit. (See attached video)

https://user-images.githubusercontent.com/26145882/145674716-b32e540d-d5e4-4879-b012-9cb396dc9fcc.mp4

Originally created by @sussycatgirl on GitHub (Dec 11, 2021). Originally assigned to: @sussycatgirl on GitHub. It appears that when a user leaves a server (or gets kicked/banned) and is not already cached, revolt.js attempts to fetch that user. If it is unable to fetch it (Usually because of missing permission), an exception is thrown. This is not a big issue in browser applications, but it almost certainly causes node.js applications such as bots to exit. (See attached video) https://user-images.githubusercontent.com/26145882/145674716-b32e540d-d5e4-4879-b012-9cb396dc9fcc.mp4
yindo added the bug label 2026-02-16 12:26:44 -05:00
yindo closed this issue 2026-02-16 12:26:44 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/javascript-client-sdk#8