-
-
Notifications
You must be signed in to change notification settings - Fork 44
Initialize asyncio event loop before using it #274
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
Python 3.14 (in Fedora 43) throws RunetimeError if event loop is not initialized before using it. Resolves: QubesOS/qubes-issues#10188
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #274 +/- ##
==========================================
- Coverage 93.09% 93.02% -0.08%
==========================================
Files 64 64
Lines 13269 13269
==========================================
- Hits 12353 12343 -10
- Misses 916 926 +10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I guess GTK already creates the event loop. |
|
To be clear - this explodes only in F42-based sys-gui, somehow it does work in F41-based dom0. |
That is correct. For the
This is related to QubesOS/qubes-issues#9809 So let's revisit the situation. If we have |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025083017-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=2025081011-4.3&flavor=update
Failed tests15 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/149225#dependencies 72 fixed
Unstable testsPerformance TestsPerformance degradation:17 performance degradations
Remaining performance tests:157 tests
|
Sounds accurate |
Python 3.14 (in Fedora 43) throws RunetimeError if event loop is not initialized before using it.
Resolves: QubesOS/qubes-issues#10188