Skip to content

Ship dashboard observation fixes in Server 2.5.9 - #311

Merged
rmcdaniel merged 2 commits into
mainfrom
fix/dashboard-observation-253
Oct 7, 2026
Merged

rmcdaniel merged 2 commits into
mainfrom
fix/dashboard-observation-253

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Changes

Ship Workflow 2.5.3's dashboard fixes through Server 2.5.9 and Helm 0.1.146.

Add HTTP regression checks for UTC projection counts in a local application and observation with database writes disabled. Expired heartbeat rows remain available to diagnostics while active-worker results exclude them.

Addresses Workflow #646 and #648. The worker protocol and SDK packages are unchanged.

Verification

The published 2.5.2 package baseline fails both new HTTP cases. With registry-installed 2.5.3, the affected metrics class passes all 22 cases / 220 assertions and Pint passes. PR and main checks pass.

Server 2.5.9 publication passes exact Docker Hub/GHCR identity checks, both architectures, first-run readiness, source-free Compose and protocol catalog. Helm 0.1.146 passes anonymous clean-cluster installation. Image index: sha256:11c11e11498b63e644d906e43f49810a1bc0b5298f750734fe0edb279c622bca.

Actual published-image full, bounded and workflow-type dashboard HTTP checks pass with Europe/Kyiv application time, PostgreSQL 17 and Redis 7. Each counts four recent runs among six UTC/legacy fixtures and one active worker. The observer login has SELECT, no INSERT/UPDATE/DELETE privileges and read-only transactions. Both active and expired heartbeat rows remain after observation.

@rmcdaniel
rmcdaniel marked this pull request as ready for review October 7, 2026 13:49
@rmcdaniel
rmcdaniel merged commit d977271 into main Oct 7, 2026
15 checks passed
@rmcdaniel
rmcdaniel deleted the fix/dashboard-observation-253 branch October 7, 2026 14:03
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.

2 participants