This repository was archived by the owner on Apr 17, 2023. It is now read-only.

Description
This is a critical bug.
Ref: onClose function
In case the websocket closes with a code that doesn't have an explicit case, such as the abnormal 1006 I just got nothing will be done. There's no default case to have it just destroy with fatal: true, reconnect: true, causing the gateway shard to enter a state where it keeps on trying to send heartbeats only for ws to throw every single time. There's no recovery that can be made from this stage.