-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes killing a deemon doesn’t work in the VS Code build #6
Comments
Fyi I see this sometimes with the following keyboard shortcut I have configured: {
"key": "cmd+shift+alt+b",
"command": "workbench.action.tasks.runTask",
"args": "Restart VS Code - Build"
} |
I can't really repro. Also, @TylerLeonhardt are you sure this is deemon related? Might actually be VS Code tasks related. This will kill both tasks from the command line:
Can you also reproduce if you just run that? |
Yeah... this must be a task thing I guess because I haven't been able to repro using that script... gonna close this until I have more understanding |
It killed one but left another running? |
Yes that's right. And if I run the command over and over again, that surviving process never dies. Doesn't happen all the time, unfortunately... So I'm not sure what the pattern is. Any thing else I can grab for you? |
@hediet and I figured out the issue! Reproduces if you have really long running builds. Fix coming up! |
fixes deemon issue joaomoreno/deemon#6
fixes deemon issue joaomoreno/deemon#6
I have encountered a problem that deemon cannot kill a task normally. I try to kill for a long time, but it can't end. hi @joaomoreno, I would like to ask if I have encountered any similar problems ? Or if it has anything to do with this problem? |
This problem appears in mac OS 12.2.1 in intel & deemon@1.7.1 |
The “Kill VS Code - Build” task doesn't seem always kill the running build task. Often it manages to kill one of 2 running, but not the other.
I’ve noticed this on macOS and some have noticed on Windows.
workaround is to find the deemon process and kill it manually.
Let me know if there’s anything else you need @joaomoreno
The text was updated successfully, but these errors were encountered: