Ignore WebSocketError::NoDataAvailable

This may turn out to be a bad idea, but this causes a reconnect, as part
of the catch-all `rust-websocket` crate error handling. Since this
variant in particular doesn't seem directly harmful to ignore, it may be
better to just throw away than to reconnect.

1 files changed, 2 insertions, 0 deletions

diff --git a/src/client/gateway/shard.rs b/src/client/gateway/shard.rs
index 4cafd21..4ebe26f 100644
--- a/src/client/gateway/shard.rs
+++ b/src/client/gateway/shard.rs
@@ -10,6 +10,7 @@ use super::super::Client;
 use super::{GatewayError, GatewayStatus, prep};
 use websocket::client::{Client as WsClient, Sender, Receiver};
 use websocket::message::Message as WsMessage;
+use websocket::result::WebSocketError;
 use websocket::stream::WebSocketStream;
 use websocket::ws::sender::Sender as WsSender;
 use ::constants::OpCode;
@@ -301,6 +302,7 @@ impl Shard {
 
                 self.reconnect(receiver).map(|(ev, rec)| Some((ev, Some(rec))))
             },
+            Err(Error::WebSocket(WebSocketError::NoDataAvailable)) => Ok(None),
             Err(Error::WebSocket(why)) => {
                 warn!("Websocket error: {:?}", why);
                 info!("Reconnecting");