Open
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
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.
Summary
This PR implements a robust graceful shutdown mechanism to ensure the backend safely drains in-flight requests and closes database connections on
SIGTERMandSIGINTsignals, preventing 502 errors during deployments or restarts.Fixes #58
Changes Made
SIGTERMandSIGINTinsidesrc/index.ts.server.close()immediately to stop accepting new HTTP requests.Set(activeConnections) to ensure critical billing and settlement requests are fully processed before the server exits.closeDb()insrc/db/index.tsand integrated it into the shutdown sequence to safely close the SQLite connection.TIMEOUT_MS) to force-exit the process if connections hang indefinitely.Testing
CTRL+C.0.process.exit(0).