Schedule synchronous function to separate thread - #312
Conversation
|
Ideally this is merged after: So I can solve the merge conflict and add necessary changes. |
|
About 561c22c, please see: QubesOS/qubes-core-admin-client#469 (comment) |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026072016-devel&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=2026050504-devel&flavor=update
Failed tests15 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 21 fixed
Unstable testsDetails
Performance TestsPerformance degradation:28 performance degradations
Remaining performance tests:83 tests
|
17ed68f to
7482948
Compare
|
I tests this PR with a qube that can shutdown normally and a freezed qube. Sometimes I set those qube to shutdown to have dependencies, so it fail with "in use" if not using force. Tested system:
Tested actions:
|
Waiting for the server to send the result of the API calls, allows dealing with failures/exceptions:
It also does not block the widget from being opened again even if an action is still running. This allows, for example:
For qui/tray/domains.py, the "widget.destroy()" is called earlier, cause it's not needed after the response is received. Else it hangs until the "react_to_question" finishes.
For: QubesOS/qubes-issues#10648
For: QubesOS/qubes-issues#10651
For: QubesOS/qubes-issues#10835
Requires: QubesOS/qubes-core-admin#807
Requires: QubesOS/qubes-core-admin-client#469