feat: add signal handling serviceweaver config #11
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
We enhanced the run method by incorporating signal handling for gracefully closing the process when receiving a SIGINT, SIGKILL, SIGTERM signals.
Also, it was added comment TODO for improve later
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added signal handling for graceful process termination and set the
SERVICEWEAVER_CONFIG environment variable if not already set.
The feature enhances the run method by incorporating signal handling
for gracefully closing the process upon receiving SIGINT, SIGKILL,
or SIGTERM signals. Additionally, a comment with a TODO was included
for potential future improvements. Also, Set MySQL driver in template
for database connections