Repository navigation
feat(runtime): per-handler shutdown timeouts (OMN-882) #613
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
Merged
jonahgabriel
merged 2 commits into
main
from
jonah/omn-882-per-handler-shutdown-timeouts
Mar 5, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 4161
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 328
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 1209
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 2699
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 14894
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 4778
🏁 Script executed:
Repository: OmniNode-ai/omnibase_infra
Length of output: 145
Handle cancellation path in pool close; without CancelledError handling, connections leak on cancellation.
The outer
handler.shutdown()call atprotocol_lifecycle_executor.py:307wraps the handler inasyncio.wait_for(handler.shutdown(), timeout=effective_timeout). If this outer timeout or task cancellation fires before the inner pool close completes, aCancelledErroris raised. SinceCancelledErrordoesn't inherit fromTimeoutError, the exception bypasses the handler at line 424, but thefinallyblock at line 435 still executes and clearsself._poolwithout callingterminate(). This leaves live database connections active.Add
except asyncio.CancelledErrorhandling to ensureterminate()is called:Suggested fix
if self._pool is not None: try: await asyncio.wait_for( self._pool.close(), timeout=_POOL_CLOSE_TIMEOUT_SECONDS ) except TimeoutError: logger.warning( "Database pool close timed out, terminating connections", extra={ "timeout_seconds": _POOL_CLOSE_TIMEOUT_SECONDS, "pool_size": self._pool_size, }, ) # Terminate remaining connections forcefully self._pool.terminate() + except asyncio.CancelledError: + logger.warning( + "Database pool close cancelled, terminating connections", + extra={"pool_size": self._pool_size}, + ) + self._pool.terminate() + raise finally: self._pool = None🤖 Prompt for AI Agents