Closed TARS-bot closed 6 years ago
Good morning @SomberNight,
I just received another crash report related to this issue. The crash occured on Electrum 3.1.3. I'm not sure which versions of Electrum include the fix but this is the first report from anything newer than 3.1.1 since you closed the issue.
Could you please check if this issue really is resolved? Here is the traceback that I just collected:
File "site-packages\electrum-3.1.3-py3.5.egg\electrum\util.py", line 794, in run_with_except_hook
File "site-packages\electrum-3.1.3-py3.5.egg\electrum\network.py", line 985, in run
File "site-packages\electrum-3.1.3-py3.5.egg\electrum\network.py", line 967, in wait_on_sockets
File "site-packages\electrum-3.1.3-py3.5.egg\electrum\network.py", line 626, in process_responses
File "site-packages\electrum-3.1.3-py3.5.egg\electrum\network.py", line 559, in process_response
TypeError: unorderable types: NoneType() > int()
~ With robotic wishes
Good morning @SomberNight,
I just received another crash report related to this issue. The crash occured on Electrum 3.2.3. I'm not sure which versions of Electrum include the fix but this is the first report from anything newer than 3.1.3 since you closed the issue.
Could you please check if this issue really is resolved? Here is the traceback that I just collected:
File "electrum/util.py", line 882, in run_with_except_hook
File "electrum/network.py", line 1085, in run
File "electrum/network.py", line 1067, in wait_on_sockets
File "electrum/network.py", line 719, in process_responses
File "electrum/network.py", line 646, in process_response
TypeError: '>' not supported between instances of 'NoneType' and 'int'
~ With robotic wishes
Note: the recent and expected future reports are due to https://github.com/kyuupichan/electrumx/pull/760
Users must update their client to be able to connect to servers.
@SomberNight please state which minimum version is needed to not have this problem
You need at least 3.2.4, but using 3.3.4+ is strongly suggested
You need at least 3.2.4, but using 3.3.4+ is strongly suggested
Thank you, works now.
Good morning @SomberNight,
I just received another crash report related to this issue. The crash occured on Electrum 5b6fe40-dirty. I'm not sure which versions of Electrum include the fix but this is the first report from anything newer than 3.2.3 since you closed the issue.
Could you please check if this issue really is resolved? Here is the traceback that I just collected:
File "site-packages\electrum-3.2.0-py3.5.egg\electrum\util.py", line 856, in run_with_except_hook
File "site-packages\electrum-3.2.0-py3.5.egg\electrum\network.py", line 1036, in run
File "site-packages\electrum-3.2.0-py3.5.egg\electrum\network.py", line 1018, in wait_on_sockets
File "site-packages\electrum-3.2.0-py3.5.egg\electrum\network.py", line 685, in process_responses
File "site-packages\electrum-3.2.0-py3.5.egg\electrum\network.py", line 612, in process_response
TypeError: unorderable types: NoneType() > int()
~ With robotic wishes
Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
Reporter
This issue was reported by 2401 user(s):
Additional Information