-
Notifications
You must be signed in to change notification settings - Fork 235
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
[pd] daemon service: reconnect to dbus on dbus reset #2605
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2605 +/- ##
==========================================
- Coverage 55.77% 45.91% -9.87%
==========================================
Files 87 106 +19
Lines 6890 12624 +5734
Branches 0 915 +915
==========================================
+ Hits 3843 5796 +1953
- Misses 3047 6511 +3464
- Partials 0 317 +317 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
7b9e92b
to
3d43baa
Compare
3d43baa
to
88e1433
Compare
740fdb5
to
b516ccd
Compare
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.
LGTM 👍
b516ccd
to
4b03dee
Compare
This commit addresses a potential issue where the pd daemon loses its dbus connection when original dbus is reset. The daemon now monitors the io.openthread.BorderRouter.wpan0 dbus name and reconnects if the name owner changes, indicating a likely otbr-agent reload. This ensures the daemon continues to function correctly after dbus is reset by otbr-agent.