feat: add API error detection and auto-recovery for peers #7
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
When a peer's CLI process is alive but API calls are failing (400, 429, 500, etc.), the current crash detection doesn't trigger because the pane isn't dead. This adds: - New module: orchestrator/api_error_recovery.py - Detects API error patterns in pane output during health checks - Auto-restarts peer when errors detected (with debounce and limits) - Notifies user via outbox when restart occurs Reuses existing restart infrastructure (count_recent_restarts, restart_peer) and follows the existing module pattern (make() factory function).
Owner
|
Thanks a lot for your PR! |
Author
|
hi, author |
Contributor
|
Hi, I feel we should let Foreman make autonomous decisions, what do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When a peer's CLI process is alive but API calls are failing (400, 429, 500, etc.), the current crash detection doesn't trigger because the pane isn't dead.
This adds:
Reuses existing restart infrastructure (count_recent_restarts, restart_peer) and follows the existing module pattern (make() factory function).