Ignored exception in destructor when pushing to ssh remote

[byaka]

DVC version 0.82.3
Platform Linux Ubuntu 18.04
Installed with pip3

Inited new repo and added some files to dvc, now im try to push them.

user@dev5:~/projects/recsys_similar_new$ dvc remote list --global
myremote	ssh://[email protected]/srv/dvc/storage
user@dev5:~/projects/recsys_similar_new$ dvc push -r myremote
Everything is up to date.                                                                                                                                 
Exception ignored in: <bound method Pool.__del__ of <dvc.remote.pool.Pool object at 0x7f7594a35f98>>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/dvc/remote/pool.py", line 42, in __del__
  File "/usr/local/lib/python3.6/dist-packages/dvc/remote/pool.py", line 46, in close
  File "/usr/local/lib/python3.6/dist-packages/dvc/remote/ssh/connection.py", line 59, in close
  File "/usr/local/lib/python3.6/dist-packages/paramiko/sftp_client.py", line 195, in close
  File "/usr/local/lib/python3.6/dist-packages/paramiko/channel.py", line 666, in close
  File "/usr/local/lib/python3.6/dist-packages/paramiko/channel.py", line 1255, in _close_internal
  File "/usr/local/lib/python3.6/dist-packages/paramiko/channel.py", line 1246, in _send_eof
  File "/usr/local/lib/python3.6/dist-packages/paramiko/message.py", line 232, in add_int
TypeError: 'NoneType' object is not callable

[efiop]

Hi @byaka !

dvc push succeeded, but there has been a hickup when the interpreter was shutting down, that doesn't really affect the functionality but is indeed really ugly. We will take a closer look ASAP.

Thanks for the feedback!

[byaka]

@efiop ah, ok, so this not a fatal error. thx for answer!

[efiop]

@byaka Btw, are you able to reliably reproduce? Or does it happen just once in a while for you?

[byaka]

no, it happens for me on every push, pull or status but only on servers where dvc installed via pip
on my centos servers dvc installed via yam and this problem not happens

[efiop]

@byaka yum packages are a bit different, they are built with pyinstaller, so it might be swallowing such hickups. Thanks for clarifying! We will try to take look soon. Let us know if you'll have any other issues 🙂

[efiop]

For the record: another user is experiencing the same issue https://discordapp.com/channels/485586884165107732/485596304961962003/672421181185589275

[e3bo]

I'm also experiencing this issue.

Ubuntu 19.04 and Arch Linux
DVC version 0.82.6.
Installed via pip

Additionally, I have gotten

Exception ignored in: <function Pool.__del__ at 0x7fb429b86e50>                                                    
Traceback (most recent call last):                                                                                 
 File "/home/eamon/venv2/lib/python3.8/site-packages/dvc/remote/pool.py", line 42, in __del__                     
 File "/home/eamon/venv2/lib/python3.8/site-packages/dvc/remote/pool.py", line 46, in close                       
 File "/home/eamon/venv2/lib/python3.8/site-packages/dvc/remote/ssh/connection.py", line 59, in close
 File "/home/eamon/venv2/lib/python3.8/site-packages/paramiko/sftp_client.py", line 195, in close
 File "/home/eamon/venv2/lib/python3.8/site-packages/paramiko/channel.py", line 671, in close
 File "/home/eamon/venv2/lib/python3.8/site-packages/paramiko/transport.py", line 1846, in _send_user_message
 AttributeError: 'NoneType' object has no attribute 'time'

following dvc pull. But this does not occur every time I run that command.

[efiop]

For the record: can reproduce with paramiko 2.5.0, 2.6.0 and 2.7.1, so it is something else that broke. Looking into it. dvc 0.80.0 indeed doesn't have that bug.

[efiop]

Guys, thanks for the feedback! The issue is fixed by #3274. We are releasing new version right now.

[efiop]

@byaka @e3bo @aprimostka Guys, 0.82.8 is out. Please upgrade and give it a try. Let us know if the issue still persists or not 🙂

[byaka]

@efiop thank u and dvc-team, new version works like a charm

[aprimostka]

I had not time to fully test but first run gone smoothly

[e3bo]

Upgrading to 82.8 from 82.6 resolved the issue for me too.