Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Scope Docker temperature test past the drawer readings strip
rcourtman2d4eb6a02a4c
diff --git a/docs/release-control/v6/internal/subsystems/storage-recovery.md b/docs/release-control/v6/internal/subsystems/storage-recovery.mdindex 5e04176f2b..855fce2de6 100644--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md@@ -648,14 +648,13 @@ datastore rows; the drawer reads them from the row's resource.Host-figure truthfulness therefore belongs to the drawer. The deletedtable-cell proof (`ProxmoxBackupServersTable.memory.test.tsx`) has no surface-left to cover, and the drawer is weaker than that cell in two known ways: its-CPU and memory percentages come from its History charts, so a failed history-read hides them where the row showed the live reading; and its shared-`getMemoryPercent` treats a measured zero used with a positive capacity as-missing and lets an invalid byte pair override a valid percentage. Those are-existing drawer behaviors on every platform, not part of this change, and are-not yet fixed; this section does not claim the drawer matches the deleted-cell's validation.+left to cover. The drawer keeps the cell's guarantees: when no History chart+can be drawn, a failed read or a locked range, its Latest readings strip still+shows the live CPU and memory with their current, last-known or+freshness-unknown qualifier; and the shared `getMemoryPercent` uses a valid+byte pair, a measured zero included, before a 0-100 percentage. Those are+shared drawer and helper behaviors on every platform, pinned by+`ResourceDetailDrawer.history.test.tsx` and `resource.test.ts`.`ProxmoxBackupServersTable.test.ts` pins that rows carry no host readings andkeep the host resource the drawer reads, and `ProxmoxBackupsTable.test.tsx`pins the column set.diff --git a/frontend-modern/src/features/docker/__tests__/DockerHostsTable.test.tsx b/frontend-modern/src/features/docker/__tests__/DockerHostsTable.test.tsxindex 89f84ea97a..5c835db553 100644--- a/frontend-modern/src/features/docker/__tests__/DockerHostsTable.test.tsx+++ b/frontend-modern/src/features/docker/__tests__/DockerHostsTable.test.tsx@@ -611,8 +611,10 @@ describe('DockerHostsTable', () => {fireEvent.click(screen.getByText('docker-01').closest('tr')!);- const drawer = screen.getByTestId('docker-host-drawer');- expect(within(drawer).getByText('76°C').closest('td')).toHaveClass(+ // The History strip repeats the reading when no chart can be drawn; the+ // threshold colour belongs to the Details row.+ const details = screen.getByTestId('docker-host-technical-details');+ expect(within(details).getByText('76°C').closest('td')).toHaveClass('text-emerald-700','dark:text-emerald-300',);