Repository navigation
Keep SiK gateways alive through CoT outages - #2
Merged
Merged
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
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.
The daemon, scan, and sentinel entry points construct custom CLITool worker graphs and therefore bypassed the standard PyTAK reconnect loop. Each now constructs a fresh client per attempt under the public PyTAK 7.5.2 supervisor. Transient CoT outages stay in-process with bounded backoff; local serial and configuration faults still reach systemd.
Validation: 7 tests pass locally, including all three entry-point reconnect wiring cases; flake8 and compileall pass on changed Python files.