Your message dated Wed, 7 Jun 2017 00:37:27 +0300
with message-id <20170606213726.ydxjf3qc3r5eb...@marvin.dmesg.gr>
and subject line Re: Bug#864296: throws StopIteration exception, then
immediately dies
has caused the Debian Bug report #864296,
regarding throws StopIteration exception, then immediately dies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
864296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-socketio-client
Version: 0.6.5-0.1
Severity: grave
Hi,
Since upgrading to stretch, python-socketio-client no longer works for me at
all.
I have code looking roughly this:
#! /usr/bin/python
from __future__ import print_function
from socketIO_client import SocketIO
from socketIO_client.exceptions import TimeoutError
with SocketIO('https://notification2.chess24.com',
transports=['xhr-polling'], verify=True) as socketIO:
pass
But all I get is this:
DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTPS connection
(1): notification2.chess24.com
DEBUG:requests.packages.urllib3.connectionpool:https://notification2.chess24.com:443
"GET /socket.io/?EIO=3&transport=polling&t=1496761595949-0 HTTP/1.1
" 200 None
Traceback (most recent call last):
File "./chess24.py", line 198, in <module>
with SocketIO('https://notification2.chess24.com', verify=True) as
socketIO:
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line
331, in __init__
resource, hurry_interval_in_seconds, **kw)
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line
51, in __init__
self._transport
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line
59, in _transport
self._engineIO_session = self._get_engineIO_session()
File "/usr/lib/python2.7/dist-packages/socketIO_client/__init__.py", line
73, in _get_engineIO_session
transport.recv_packet())
StopIteration
It seems there is indeed a stray “break” on line 73 that isn't caught by any
exception handler. Downgrading to jessie immediately fixes the problem.
WebSockets vs. XHR transport doesn't make a difference.
-- System Information:
Debian Release: 9.0
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (500,
'stable')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.2 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-socketio-client depends on:
ii python 2.7.13-2
ii python-requests 2.12.4-1
ii python-six 1.10.0-3
ii python-websocket 0.37.0-2
python-socketio-client recommends no packages.
python-socketio-client suggests no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Hi,
On 17:18 Tue 06 Jun , Steinar H. Gunderson wrote:
> Package: python-socketio-client
> Version: 0.6.5-0.1
> Severity: grave
>
> Hi,
>
> Since upgrading to stretch, python-socketio-client no longer works for me at
> all.
> I have code looking roughly this:
>
> #! /usr/bin/python
> from __future__ import print_function
> from socketIO_client import SocketIO
> from socketIO_client.exceptions import TimeoutError
> with SocketIO('https://notification2.chess24.com',
> transports=['xhr-polling'], verify=True) as socketIO:
> pass
Thanks for the report!
Looking at the message emitted by notification2.chess24.com ("Welcome to
socket.io."), it uses the old 0.9 socket.io protocol. Major socket.io
protocols are not backwards compatible and this version of
python-socketio-client supports only the 1.x socket.io protocol.
Unfortunately there's not much we can do about this since it's
upstream's decision to only support 1.x at this time. You should instead
use 0.5.7.2 (e.g. via pip) to talk to sites using the 0.9 protocol
version.
I'm closing this bug since the incompatibility is documented in the
package's changelog.
Regards,
Apollon
--- End Message ---
