Open Bessonov opened 3 years ago
I use wait-on to wait for a server between restarts:
await waitOn({ resources: [`tcp:${publicIp}:22`], delay: 5000, timeout: 60000, })
After completion it seems like connections are not closed completely:
import wtf from 'wtfnode' [...] wtf.dump()
Outputs a long list:
[WTF Node?] open handles: - File descriptors: (note: stdio always exists) - fd 2 (tty) (stdio) - fd 1 (tty) (stdio) - Sockets: - 172.30.0.2:50814 -> undefined:undefined - Listeners: - connect: (anonymous) @ /home/workspace/infra/node_modules/.pnpm/wait-on@5.2.0/node_modules/wait-on/lib/wait-on.js:352 - 172.30.0.2:50816 -> undefined:undefined - Listeners: - connect: (anonymous) @ /home/workspace/infra/node_modules/.pnpm/wait-on@5.2.0/node_modules/wait-on/lib/wait-on.js:352 [...]
Where the line 352 matches v5.2.0/lib/wait-on.js#L352. I've tried with destroy:
destroy
.on('connect', () => { output(` TCP connection successful to host:${host} port:${port}`); conn.end(); conn.destroy(); resolve(true); });
It helps (not tested with error/timeout), but I'm not sure that this is the way to go. May be it's something not well documented, because other people experience this too.
I use wait-on to wait for a server between restarts:
After completion it seems like connections are not closed completely:
Outputs a long list:
Where the line 352 matches v5.2.0/lib/wait-on.js#L352. I've tried with
destroy
:It helps (not tested with error/timeout), but I'm not sure that this is the way to go. May be it's something not well documented, because other people experience this too.