SIGNREQUEST output in Jest about ssh2-streams HOT 5 OPEN

Since that library is not using ssh2-streams directly, I would suggest having the sftp-promises maintainer upgrade their dependency on ssh2 first and if the issue persists, lodge an issue on the ssh2 repo instead.

from ssh2-streams.

I just refactored to use ssh2-sftp-client and I'm getting the same issue due another issue with ssh2. Thanks for pointing that out.

from ssh2-streams.

@lvl99 Running into the same issue here. Did you figure it out?

from ssh2-streams.

@ArnoSoontjens can't remember how I solved this, sorry -- my GCB project is still broken, but for another reason!

I may have tried to refactor so that I didn't import any internal module that uses the SFTP dependency in my tests. Otherwise, the last thing I remember updating was changing internal SFTP module to use bottleneck to prevent too many concurrent sessions being open.

I also have a vague feeling SIGNREQUEST might be a package or something that needs explicit consent to do something? Wish I could remember!

from ssh2-streams.

Also seeing the same issue, Jest failing to exit due to open handle at ssh2 constants: testcontainers/testcontainers-node#346

from ssh2-streams.