The guest table marks with ! each guest that no backup job covers.
The frame's bottom border shows the count, for example "mainframe · 2 without backup job".
The data comes from Proxmox's own list (get cluster not-backed-up). It therefore also counts jobs that select guests by pool, which the app's own job matching does not handle.
If the coverage call fails, the guests are still listed and a warning says the coverage is unknown.
Verification
277 tests pass on this branch (cv4pve-cli is mocked).
ruff check and ruff format --check report no issues.
betterleaks found no secrets.
Read-only live check on mainframe: not-backed-up returned an empty list, so no marks and no count were shown. Every guest there is covered, so a real positive has not been seen live.
## What
- The guest table marks with `!` each guest that no backup job covers.
- The frame's bottom border shows the count, for example "mainframe · 2 without backup job".
- The data comes from Proxmox's own list (`get cluster not-backed-up`). It therefore also counts jobs that select guests by pool, which the app's own job matching does not handle.
- If the coverage call fails, the guests are still listed and a warning says the coverage is unknown.
## Verification
- 277 tests pass on this branch (`cv4pve-cli` is mocked).
- `ruff check` and `ruff format --check` report no issues.
- `betterleaks` found no secrets.
- Read-only live check on mainframe: `not-backed-up` returned an empty list, so no marks and no count were shown. Every guest there is covered, so a real positive has not been seen live.
Closes #9
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The guest table marks with "!" each guest that Proxmox's not-backed-up
list returns. The frame's bottom border shows the count, e.g.
"mainframe · 2 without backup job". This uses Proxmox's own answer, so
it also counts jobs that select guests by pool.
If the coverage call fails, the guests are still listed and a warning
says the coverage is unknown.
Closes#9
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
!each guest that no backup job covers.get cluster not-backed-up). It therefore also counts jobs that select guests by pool, which the app's own job matching does not handle.Verification
cv4pve-cliis mocked).ruff checkandruff format --checkreport no issues.betterleaksfound no secrets.not-backed-upreturned an empty list, so no marks and no count were shown. Every guest there is covered, so a real positive has not been seen live.Closes #9
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com