From 7903f6fbfca54f1a403e9e92fb4812cbe85f6621 Mon Sep 17 00:00:00 2001 From: Subv Date: Fri, 10 Apr 2020 18:35:14 -0500 Subject: [PATCH] Warnings/Network: Handle ENET_EVENT_TYPE_NONE and ENET_EVENT_TYPE_CONNECT in the network packet loop. ENET_EVENT_TYPE_NONE is basically a no-op. ENET_EVENT_TYPE_CONNECT should not happen since we are already connected. Assert in case we do receive it. --- src/network/room_member.cpp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/network/room_member.cpp b/src/network/room_member.cpp index 5814fe12a..e43004027 100644 --- a/src/network/room_member.cpp +++ b/src/network/room_member.cpp @@ -242,6 +242,13 @@ void RoomMember::RoomMemberImpl::MemberLoop() { SetError(Error::LostConnection); } break; + case ENET_EVENT_TYPE_NONE: + break; + case ENET_EVENT_TYPE_CONNECT: + // The ENET_EVENT_TYPE_CONNECT event can not possibly happen here because we're + // already connected + ASSERT_MSG(false, "Received unexpected connect event while already connected"); + break; } } {