This message was deleted.
# report-bugs
s
This message was deleted.
j
thanks for reporting — one of us noticed something similar the other day
I wonder if VSCode sets some node-related flag or environment variable we aren't expecting...
Out of curiosity, any particular reason you're running graphite commands from the debug terminal?
b
I exclusively use the JS debug terminal when in VSCode. The experience of having everything debuggable has honestly been pretty magical. Not just our own code, but build tools, test runners, etc. Our own internal CLI tools are also written in TypeScript/Node using OCLIF, but they don’t leave zombie processes. It’s probably a library you’re using or something else tied to the upgrade prompt check you have.
After killing all the zombie processes, I’ve noticed that sometimes all
gt
commands start to hang. Restarting the terminal fixes it. This doesn’t always happen. Is there maybe a daemon that gets kicked off on first run?
j
we're just using a very simple
child_process.spawn
to send a network request and save the recommended version to disk 😬 , but maybe there's something not getting cleaned up