New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with Deluge 2.0 #40
Comments
Any news? |
The warnings are caused by the version probe. In concrete, the lines 122 and 123. deluge-client/deluge_client/client.py Line 122 in 0c2e5a9
I fixed my issues by patching deluge-client and commenting those lines. Since Deluge 2.1.1 is the latest version and all users will update eventually, you should consider improving that code to not hit the warnings. For example: # test the latest version first 2.1
try:
self._send_call(2, 1, 'daemon.info')
# set small socket timeout here
result = self._socket.recv(1)
if ord(result[:1]) == 1:
self.deluge_version = 2
self.deluge_protocol_version = 1
# If we need the specific version of deluge 2, this is it.
daemon_version = self._receive_response(2, 1, partial_data=result)
return
catch:
pass
# test 2.0
# test 1.x Update 2: |
Got the same errors in my logs. |
The only user of this fork is deluge_exporter, which has already dropped support for Deluge 1. Users that were running pre-releases of Deluge 2 will most likely have upgraded to 2.0.0 or later at this point. This fixes: JohnDoee#40 tobbez/deluge_exporter#22 There's also a ticked filed against Deluge for adding a proper way to determine a daemon's protocol version, which (if implemented) would make it easier to support multiple protocol versions in the future: https://dev.deluge-torrent.org/ticket/3609
I'm running Flexget in a docker container with cpoppema/docker-flexget:latest:
I'm running deluge in a docker container with linuxserver/deluge:latest, currently version 2.0.3-2-201906121747-ubuntu18.04.1 (tested back to the earliest 2.0.0 image they had).
I seem to only see this for some torrents, I think larger ones or ones with more files (others get added perfectly fine), but in flexget I see the following log lines from deluge-client (I manually updated the log level to get the debug info):
In the deluge log, I see:
It seems deluge-client is correctly determining the protocol version, but deluge is still pissed off about it.
Related issues:
The text was updated successfully, but these errors were encountered: