Question: Why is command line still open after closing websocket connection? about bybit-api

[tiagosiebler]

I think I see why this is happening. The ws client has a dependency on the REST client:
https://github.com/tiagosiebler/bybit-api/blob/master/src/websocket-client.ts#L217-L225

This is primarily for the time offset (used during authentication as part of the timestamp sent to the server). The REST client has a timer running (for the timestamp offset) that queries the time endpoint at intervals to estimate latency. That timer must be keeping the process running.

If you do want to close the process, why not call process.exit()?
https://nodejs.org/api/process.html#processexitcode

[doppelgunner]

you are a genius!!!

[zhaoxiaohai]

I think I see why this is happening. The ws client has a dependency on the REST client: https://github.com/tiagosiebler/bybit-api/blob/master/src/websocket-client.ts#L217-L225

This is primarily for the time offset (used during authentication as part of the timestamp sent to the server). The REST client has a timer running (for the timestamp offset) that queries the time endpoint at intervals to estimate latency. That timer must be keeping the process running.

If you do want to close the process, why not call process.exit()? https://nodejs.org/api/process.html#processexitcode

Is there any other way to just shut it down? I also need the process to continue running, just temporarily closing the connection