Use glib's native asyncio integration when available#56
Use glib's native asyncio integration when available#56marmarek merged 2 commits intoQubesOS:masterfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #56 +/- ##
==========================================
- Coverage 81.44% 79.46% -1.98%
==========================================
Files 22 23 +1
Lines 2387 2518 +131
==========================================
+ Hits 1944 2001 +57
- Misses 443 517 +74 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025060102-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025031804-4.3&flavor=update
Failed tests10 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/132953#dependencies 14 fixed
Unstable testsDetails
Performance TestsPerformance degradation:11 performance degradations
Remaining performance tests:45 tests
|
|
This doesn't work very well: |
Glib >= 3.50 has native asyncio integration. When available, use it instead of gbulb. This requires few minor changes: - asyncio.run() doesn't work there (asyncio.set_event_loop() cannot be called on the main thread with glib...) - gbulb needs explicit loop.run_forever()/loop.run_until_complete() to start the loop, the Glib version does it implicitly in app.run() QubesOS/qubes-issues#9809
The loop is already running at this point. This apparently didn't exploded with gbulb, but glib's asyncio loop raises an exception in this case. QubesOS/qubes-issues#9807
Glib >= 3.50 has native asyncio integration. When available, use it
instead of gbulb.
This requires few minor changes:
called on the main thread with glib...)
QubesOS/qubes-issues#9809