This repository was archived by the owner on Sep 13, 2025. It is now read-only.
Added signal handling for graceful shutdown #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replaced blocking accept() loop with tokio::select! to handle SIGTERM and SIGINT signals. This allows the process to exit cleanly instead of being forcibly killed. Unlike the Docker workaround in 215d32c (iv-org#20), this solution fixes the issue at the application level and works in all environments (Docker, Kubernetes, bare metal) without relying on external process managers.
|
Fixes #31 |
Docker-only workaround not needed anymore since 6cd32c9.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaced blocking accept() loop with tokio::select! to handle SIGTERM and SIGINT signals. This allows the process to exit cleanly instead of being forcibly killed.
Unlike the Docker workaround in 215d32c (#20), this solution fixes the issue at the application level and works in all environments (Docker, Kubernetes, bare metal) without relying on external process managers.