Closed KeKs0r closed 4 years ago
Thanks for the detailed report. A quick analysis shows that this is not an issue with catbox. The process is exited as it should, without waiting for any previously scheduled timer. The logging from why-is-node-running
must be incorrect.
thanks for coming back so quick. I investigated further, and it turns out, if I wrap the log into a
setImmediate(log)
the handle from catbox is cleaned up.
I guess I need to go into the Jest space and see why it is complaining about open handles there. Thanks for the feedback.
Support plan
Context
What are you trying to achieve or the steps to reproduce?
After stopping the cache client, there are still open handles open from catbox
What was the result you got?
After running this script, even after stopping the cacheClient this handle was still open:
Full log output can be found in the readme in my repdroduction repo: https://github.com/KeKs0r/catbox-open-handle
What result did you expect?
That after stopping the cache client the timer should be cleaned.