-
Notifications
You must be signed in to change notification settings - Fork 18
Problem: dbus call were not async #595
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
Conversation
dbus call to systemd were not called asyncronously. Modify all call to asynchronous, this required switching from python-dbus to dbus-fast which offer an asyncio backend.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #595 +/- ##
==========================================
+ Coverage 43.83% 44.04% +0.21%
==========================================
Files 55 55
Lines 4944 5018 +74
Branches 585 594 +9
==========================================
+ Hits 2167 2210 +43
- Misses 2658 2683 +25
- Partials 119 125 +6 ☔ View full report in Codecov by Sentry. |
Failed to retrieve llama text: POST 504: 504 Gateway Time-outThe server didn't respond in time. |
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.
This seem to bring nice properties in addition to fixing the core issues.
Looks like you wrote a lot of Systemd specific boilerplate 🤔
Is there an easy way to push that upstream ?
Upstream is a generic lib for dbus and not fixated on any particular interface. I could split this in another python file if you prefer |
dbus call to systemd were not called asyncronously and thus were hanging the whole thing
Modify all call to asynchronous, this required switching from
python-dbus to dbus-fast which offer an asyncio backend.
Another adventage of dbus-fast is that is in pure python so won't require libdbus or compilation (also it is packaged in ubuntu & debian )