关于flask_socketio总是断掉

[Sunyingbin]

您好，我按照您的实现方式写了一个while死循环，没过一会儿就断了，然后就重新连接，我是自己写的一个请求，传参这种，为什么会断呢？下面是断掉后打印的log

127.0.0.1 - - [13/Nov/2020 16:34:32] "GET /socket.io/?EIO=3&transport=websocket&sid=077dbe01e0574c94915a00cf01af67b3 HTTP/1.1" 200 0 84.709405
2020-11-13 16:34:33,150-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet OPEN data {'sid': 'e2bac2e578e34e9383506d9be7e138a6', 'upgrades': ['websocket'], 'pingTimeout': 60000, 'pingInterval': 25000}
2020-11-13 16:34:33,150-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet MESSAGE data 0
127.0.0.1 - - [13/Nov/2020 16:34:33] "GET /socket.io/?EIO=3&transport=polling&t=NN0lUet HTTP/1.1" 200 349 0.001994
client connected.
2020-11-13 16:34:33,164-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet MESSAGE data 0/dcenter,
2020-11-13 16:34:33,166-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet MESSAGE data 0/dcenter
127.0.0.1 - - [13/Nov/2020 16:34:33] "POST /socket.io/?EIO=3&transport=polling&t=NN0lUf4&sid=e2bac2e578e34e9383506d9be7e138a6 HTTP/1.1" 200 219 0.001954
127.0.0.1 - - [13/Nov/2020 16:34:33] "GET /socket.io/?EIO=3&transport=polling&t=NN0lUfC&sid=e2bac2e578e34e9383506d9be7e138a6 HTTP/1.1" 200 194 0.000000
(14528) accepted ('127.0.0.1', 60614)
2020-11-13 16:34:33,473-INFO: e2bac2e578e34e9383506d9be7e138a6: Received request to upgrade to websocket
127.0.0.1 - - [13/Nov/2020 16:34:33] "GET /socket.io/?EIO=3&transport=polling&t=NN0lUfM&sid=e2bac2e578e34e9383506d9be7e138a6 HTTP/1.1" 200 183 0.297349
2020-11-13 16:34:33,476-INFO: e2bac2e578e34e9383506d9be7e138a6: Upgrade to websocket successful
2020-11-13 16:34:58,180-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:34:58,180-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:35:23,194-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:35:23,194-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:35:48,200-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:35:48,200-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:36:13,204-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:36:13,204-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:36:38,215-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:36:38,215-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:37:03,228-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:37:03,228-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:37:28,246-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:37:28,246-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:37:53,250-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:37:53,250-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:38:18,255-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:38:18,255-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:38:43,268-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:38:43,268-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:39:08,274-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:39:08,274-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:39:33,291-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None
2020-11-13 16:39:33,291-INFO: e2bac2e578e34e9383506d9be7e138a6: Sending packet PONG data None
2020-11-13 16:39:58,307-INFO: e2bac2e578e34e9383506d9be7e138a6: Received packet PING data None