Fix shards attempting to re-identify on their own

Fix shards by taking away their responsibility to re-identify, instead
shutting down shard runners and going through the shard queuer to
restart a shard runner and its associated shard.

This fixes the case where a running shard's session invalidates and
re-IDENTIFYs within 5 seconds before queued shard starts, causing a
cascading failure of sessions for new shards.

1 files changed, 8 insertions, 2 deletions

diff --git a/src/gateway/mod.rs b/src/gateway/mod.rs
index 7e4e2b0..a6de656 100644
--- a/src/gateway/mod.rs
+++ b/src/gateway/mod.rs
@@ -148,9 +148,15 @@ impl ConnectionStage {
 }
 
 pub enum ShardAction {
-    Autoreconnect,
     Heartbeat,
     Identify,
-    Reconnect,
+    Reconnect(ReconnectType),
+}
+
+/// The type of reconnection that should be performed.
+pub enum ReconnectType {
+    /// Indicator that a new connection should be made by sending an IDENTIFY.
+    Reidentify,
+    /// Indicator that a new connection should be made by sending a RESUME.
     Resume,
 }