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

HTTP server doesn't shut down when process is exited #20

Open
vadimdemedes opened this issue Jul 9, 2024 · 2 comments
Open

HTTP server doesn't shut down when process is exited #20

vadimdemedes opened this issue Jul 9, 2024 · 2 comments

Comments

@vadimdemedes
Copy link

When my Go program contains a net/http server and process is exited via Ctrl + C or q, the process apparently keeps hanging around, because when I restart the program, the port is still taken. Interestingly, this doesn't happen when the same program is ran without dispatch run.

@chicoxyzzy
Copy link

I think that this is an issue with CLI (https://github.com/dispatchrun/dispatch). @chriso is that correct? And if so, should we transfer the issue to the CLI repo?

@chriso
Copy link
Contributor

chriso commented Jul 10, 2024

This would definitely be an issue upstream in the CLI.

@vadimdemedes @chicoxyzzy what version of the CLI are you using? Can you confirm that you're using a version that includes the fixes from dispatchrun/dispatch#75? I thought I fixed all the signal related issues but maybe not.

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

3 participants