Skip to content
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

deno task doesn't handle signals correctly (repro comparison with npm run attached) #26834

Open
mo opened this issue Nov 12, 2024 · 1 comment

Comments

@mo
Copy link

mo commented Nov 12, 2024

Version: Deno 2.0.6

deno tasks doesn't handle signals properly (but npm scripts do). I created a simple repro for issue here:
https://github.com/mo/deno-tasks-signal-issue-repro

./docker-compose.sh and "npm run docker-compose" both exit immediately when CTRL-C is press twice.

However, "deno task docker-compose" will instead exit deno but leave docker compose running for the full 10sec grace period while printing the docker compose progress spinner onto my shell prompt.

Deno task should just work like npm run instead.

@dsherret
Copy link
Member

Duplicate of #18445 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants