You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using git version (master) of the ssh2-python, the sftp open code doesn't handle the LIBSSH2_ERROR_EAGAIN and raise it as an error (since c2e5381)
I made a small patch which fix the issue on my local setup, which was raising all the time an error when trying to use sftp, because of the LIBSSH2_ERROR_EAGAIN, but this is probably but the most efficient way you want to commit (this is why I didn't made any Pull Request).
Uh oh!
There was an error while loading. Please reload this page.
Using git version (master) of the
ssh2-python
, the sftp open code doesn't handle theLIBSSH2_ERROR_EAGAIN
and raise it as an error (since c2e5381)I made a small patch which fix the issue on my local setup, which was raising all the time an error when trying to use sftp, because of the
LIBSSH2_ERROR_EAGAIN
, but this is probably but the most efficient way you want to commit (this is why I didn't made any Pull Request).The patch: maxux@7dc3833
Based on the C exemple here: http://yoyakuweb.com/lib/libssh2-1.4.3/libssh2-1.4.3/example/sftp_nonblock.c
Some
waitsocket
workaround should be done and not a loop like me.Anyway, the
LIBSSH2_ERROR_EAGAIN
should definitively be handled during sftp open call.The text was updated successfully, but these errors were encountered: