Skip to content
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

client.put silently hangs in node 10 #284

Open
MadaraUchiha opened this issue May 27, 2018 · 12 comments
Open

client.put silently hangs in node 10 #284

MadaraUchiha opened this issue May 27, 2018 · 12 comments

Comments

@MadaraUchiha
Copy link

Using the latest version, calling ftpClient.put('/local/path', '/remote/path', console.log) never returns. In debug mode, I also get the following warning: [DEP0016] DeprecationWarning: 'GLOBAL' is deprecated, use 'global'

When moving back to node 9, it works fine.

@john30
Copy link

john30 commented Jun 26, 2018

similar for client.get(url, localFile, callback): it never retrieves any byte and at some point fails with timeout. all fine on node 9, broken on node 10.5
when using the client.get(url, callback: (err, socket)) variant, the readable event occurs just once on node 10.5, but almost permanently on node 9

@john30
Copy link

john30 commented Jun 29, 2018

problem with client.get verified to exist on node versions 10.1.0, 10.3.0, 10.4.0
verified to be working fine on node versions 9.4.0 and 9.11.2

@blackshadev
Copy link

Will be fixed in my pull request. Apparently Node 10 changed the flowMode of streams. I checked the change logs and found the following: [cf5f9867ff] - (SEMVER-MAJOR) stream: 'readable' have precedence over flowing. So that's the culprit. This is a relative bug and breaking change, even though it isn't highlighted in NodeJS changelog summery.

@worksofliam
Copy link

@blackshadev Has this been merged? I have just updated to Node 10.8.0 and I'm having the same issue.

Thanks!

@blackshadev
Copy link

@worksofliam nope, and I haven't received any word from the author yet.

@worksofliam
Copy link

@sergi Please update us here. Thanks.

@mikeqoo1
Copy link

Nice PR

@rvarbanov
Copy link

@blackshadev there seems to be an issue with your PR. Would you please take a look?

@blackshadev
Copy link

blackshadev commented Sep 14, 2018

Sorry but I am unable to look into in very soon. Maybe someone else can? The PR was really simple since the bug is pretty straight forward. @sergi can you help ?

@rvarbanov
Copy link

It would be great if someone can add a fix as I will have to do a production hotfix and downgrade node js to version 9. I would love it if I didn't have to do that. :<

@jazoom
Copy link

jazoom commented Oct 6, 2018

In case this helps someone else, I have found a nice new FTP client. I'd rather change FTP client at this point than drop back to Node 8.

It is currently being actively maintained, has 0 dependencies (jsftp has 6 dependencies), is promise-based, has type annotations, and works on Node 10.

https://github.com/patrickjuchli/basic-ftp

@worksofliam
Copy link

Hi

Just as a note, this is also happening with the .get method.

Thanks,
Liam Barry

Jkovarik added a commit to nasa/cumulus that referenced this issue Dec 16, 2019
Jkovarik added a commit to nasa/cumulus that referenced this issue Dec 17, 2019
* Update refs to node 10

* Update all terraform lambda env targets to node10.x
* Update all node references to 10.16.3 (AWS lambda env)
* Update all aws-sdk version references to ^2.585.0
* Explicitly pin ssh2-streams to ^0.4.8

* Add unit tests for es log object parsing

* Minor refactor

* Update Cumulus to use CMA 1.1.2, cumulus-message-adapter-js 1.1.0

* Update docs/refs to node 8

* Fix logging output

* Temporary fix for issue with jsftp (sergi/jsftp#284)

* Update CHANGELOG
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants