A new "Resources" section at the top of the info screen shows:
CPU cores, with sockets for VMs (for example "4 cores × 2 sockets"). A container without a cores limit shows "unlimited".
Memory in MiB, and swap for containers.
Each disk with its size. These are the same disks the edit dialog offers, so cloud-init and CD drives are left out.
These are configured values, not usage. An open info screen reloads after any guest job, so values changed with e show up straight away.
Verification
272 tests pass, including new tests for VM resources, container resources with swap and mount points, the "unlimited" case, and the reload after an edit.
ruff check and ruff format --check report no issues.
betterleaks found no secrets.
Live check with read-only calls: CT 104 shows 1 core, 512 MiB memory, 512 MiB swap and rootfs 2G.
## What
A new "Resources" section at the top of the info screen shows:
- CPU cores, with sockets for VMs (for example "4 cores × 2 sockets"). A container without a cores limit shows "unlimited".
- Memory in MiB, and swap for containers.
- Each disk with its size. These are the same disks the edit dialog offers, so cloud-init and CD drives are left out.
These are configured values, not usage. An open info screen reloads after any guest job, so values changed with `e` show up straight away.
## Verification
- 272 tests pass, including new tests for VM resources, container resources with swap and mount points, the "unlimited" case, and the reload after an edit.
- `ruff check` and `ruff format --check` report no issues.
- `betterleaks` found no secrets.
- Live check with read-only calls: CT 104 shows 1 core, 512 MiB memory, 512 MiB swap and rootfs 2G.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new "Resources" section at the top of the info screen shows CPU
cores (with sockets for VMs), memory, swap for containers, and each
disk with its size. The disks are the same ones the edit dialog
offers, so cloud-init and CD drives are left out. A container without
a cores limit shows "unlimited".
The open info screen reloads after any guest job, so values edited
with e show up straight away.
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
A new "Resources" section at the top of the info screen shows:
These are configured values, not usage. An open info screen reloads after any guest job, so values changed with
eshow up straight away.Verification
ruff checkandruff format --checkreport no issues.betterleaksfound no secrets.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com