Repository navigation
Recover Bluetooth transport after controller loss - #6
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
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.
A removed controller left the daemon serving RPC and logging failed advertisement rotations indefinitely. Detect controller removal and lost advertising, invalidate transport readiness, and exit so the managed service rebuilds GATT and rotating advertising on the available controller. Keep retrying while the controller is absent and reload the existing bond on recovery.
Expose optional
daemon.transport_readyin Status RPC and CLI JSON, independently of RPC liveness and phone presence. Ordinary unanswered approvals do not trigger recovery. The panel consumer is dmytrogajewski/sy#9.Validation:
make lintandmake testpass in the isolated PR worktree (460 passing results, zero failures, 10 ignored). A private D-Bus integration test drives the real daemon through hci0 removal, failure exit, and relaunch on hci1, checking bond hydration and unchanged bond/key bytes. Native RPM build and package verification pass. The installed daemon advertised, the phone resubscribed, and a fresh sudo challenge succeeded through phone approval in 2.135 seconds; all seven bond/key files retained their original contents, ownership, and modes.All applicable GitHub CI checks pass for commit
82f9b01, including lint, workspace tests, release build, and documentation: https://github.com/Mewplane/syauth/actions/runs/42307576078