-
-
Notifications
You must be signed in to change notification settings - Fork 656
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
SIGINT from docker is ignored #624
Comments
Can't reproduce, here it seems sigint causes a typer-based script to close just fine. You're probably not running it right in docker, or you have something else intercepting the signals. Notably if you use |
I'm using |
Ok, I can see that you have a 466 line script with a ton of libraries and some threading stuff, too. Usually when submitting a bug to an upstream project, it's a good idea to have a minimal piece of code that demonstrates the issue very clearly. What you have is a "haystack" where you are claiming the "needle" is typer, but I don't really think that's true, or at least it is not demonstrated here in any way. |
I've had this happen in other private repos where I also use typer, and I know that typer has some handling code for sigint, so I thought I could get some help here. I've tried to isolate to isolate the issue and it seems to be related with docker compose. Even this times out at 10s when running services:
alpine-sh:
image: alpine
entrypoint: [ "sh", "-c", "while true; do sleep 10; done;" ] Thanks for the help. I'm closing this, as it doesn't seem to be related. |
Read the title. These templates for issues are worse than most eulas.
My cli applications written with typer don't handle sigints sent by docker.
The text was updated successfully, but these errors were encountered: