Ensure oz_worker_tasks_max_concurrent is primed at startup.#88
Merged
vorporeal merged 1 commit intoJun 18, 2026
Merged
Conversation
seemeroland
approved these changes
Jun 18, 2026
vorporeal
deleted the
david/ensure-max-concurrent-metric-is-primed-at-startup
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Prime
oz_worker_tasks_max_concurrentat metrics initialization so the series is available immediately, including when the worker uses the default unlimited concurrency value of0. Normal startup still records the resolved worker configuration afterward; this adds defense-in-depth and regression coverage for the gauge.Testing
go test ./internal/metricsCo-Authored-By: Oz oz-agent@warp.dev