fix: allow bounded IBKR readiness recovery to complete - #129
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Pigbibi
force-pushed
the
fix/keepalive-readiness-budget
branch
from
August 27, 2026 19:01
3ddb4d1 to
b6f518f
Compare
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
1 participant
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.
Why\n\nThe keepalive deploy job was cancelled at its 60-minute runner limit while the existing bounded, progress-aware IB Gateway readiness flow was still active. This can leave the deployment without a conclusive result even though the remote gateway remains healthy.\n\n## Change\n\n- give the deploy job 75 minutes, covering the documented maximum readiness budget and its cleanup trap\n- preserve the existing fail-closed recovery, watcher failsafe, and no-reset-on-manual-dispatch rules\n- add a workflow contract assertion\n\n## Validation\n\n- \n-