Skip to content

fix: container detail shows live CPU/Mem + adds Network/Disk I/O (0.1.40-beta6) - #205

Merged
nofuturekid merged 1 commit into
mainfrom
fix/container-detail-live-stats
May 30, 2026
Merged

nofuturekid merged 1 commit into
mainfrom
fix/container-detail-live-stats

Conversation

@nofuturekid

Copy link
Copy Markdown
Owner

The container detail sheet showed 0 for CPU/Memory because it read the polled Container fields (hardcoded 0) instead of the live dockerContainerStats overlay; now it pulls live stats from dockerLiveStats[id] (reactive) and additionally surfaces Network I/O (netIO, RX/TX) and Disk I/O (blockIO, read/write) which the subscription already delivered but the mapper dropped; rows unchanged; builds on the 0.1.40 cycle (ADR-0044).

🤖 Generated with Claude Code

The detail sheet read CPU/Memory off the polled Container (c.cpu/c.memMb),
which GetDockerContainers hardcodes to 0 — so running containers showed 0%.
Feed it the dockerContainerStats overlay instead (reactive: the open sheet
recomposes as frames land), and carry netIO/blockIO — already selected by
the subscription op but dropped by the mapper — through ContainerLiveStats
so the sheet can add Network and Disk I/O blocks. Stopped/no-frame -> "—".

ADR-0044. Docker tab rows unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@nofuturekid
nofuturekid merged commit 07d6735 into main May 30, 2026
8 checks passed
@nofuturekid
nofuturekid deleted the fix/container-detail-live-stats branch May 30, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant