-
-
Notifications
You must be signed in to change notification settings - Fork 44
Mark VMs with prohibit-start feature in updater
#247
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #247 +/- ##
==========================================
+ Coverage 93.16% 93.30% +0.13%
==========================================
Files 58 58
Lines 11065 11135 +70
==========================================
+ Hits 10309 10389 +80
+ Misses 756 746 -10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
0f25659 to
6c29022
Compare
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025031404-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=2025021804-4.3&flavor=update
Failed tests25 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/129058#dependencies 10 fixed
Unstable testsPerformance TestsPerformance degradation:32 performance degradations
Remaining performance tests:40 tests
|
|
We discussed this PR with @marmarek and he says that there are some cases where this can be misleading and that it would be better to have the VM listed, but unselectable with a "start prohibited" state. I'm not sure, what do you think about it? |
Sure. Same here. But I am clueless about what CSS effect would be right. I tried many combinations and none worked well. |
|
Wait, does this happen on master branch to you, or is the outline problem happening with your patch? If this is a general bug, I think it should got its issue and be solved separately. If it's just here, I think maybe there's just too many moving parts in making tooltips look well, and colored tooltips are just not the way to go, and it might be a better idea to give up on them and keep them default? Sorry if it was disscussed in matrix, I can't find the discussion in there because search in matrix is really pants :/ |
Master branch. Not my patch.
OK.
No. All tooltips are broken. Including the existing ones on the main branch |
0a19cb6 to
99a3394
Compare
aa49deb to
ac2dcaf
Compare
|
This is finally done. CI is green. Codecov is green, Python black is green. |
Now that we found the correct CSS selectors and current values for the tooltips (here), we can make them any color, with any background color, box border color/width, rounded or ordinary corners, font, ... I can make another commit to this PR just for tooltip CSS. |
Related: QubesOS/qubes-issues#9622