Skip to content

Fix missing worker Prometheus metrics after early startup scrapes - #9378

Open
GeorgiaPreda wants to merge 2 commits into
dask:mainfrom
GeorgiaPreda:fix-worker-prometheus-startup
Open

GeorgiaPreda wants to merge 2 commits into
dask:mainfrom
GeorgiaPreda:fix-worker-prometheus-startup

Conversation

@GeorgiaPreda

@GeorgiaPreda GeorgiaPreda commented Oct 23, 2026 •

Copy link
Copy Markdown

Hey! I have an RFC for this issue: basically it accepts an empty, non-None digest dictionary and caches the collector only after successful registration, allowing a later request to retry after failure. Added 2 regression tests

@github-actions

Copy link
Copy Markdown
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    40 files  ± 0      40 suites  ±0   14h 4m 50s ⏱️ - 17m 45s
 4 162 tests + 2   3 982 ✅ + 1    178 💤 ± 0  2 ❌ +1 
80 999 runs  +40  76 744 ✅ +25  4 253 💤 +14  2 ❌ +1 

For more details on these failures, see this check.

Results for commit ff3fde2. ± Comparison against base commit dc182bd.

@GeorgiaPreda GeorgiaPreda changed the title [unsupervised AI] Fix missing worker Prometheus metrics after early startup scrapes Fix missing worker Prometheus metrics after early startup scrapes Oct 26, 2026
@GeorgiaPreda
GeorgiaPreda marked this pull request as ready for review October 26, 2026 01:12

This branch has not been deployed

No deployments
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