chore: get docker compose working again#4246
chore: get docker compose working again#4246MasterPtato wants to merge 1 commit into02-19-fix_epoxy_make_quorum_sizes_match_paperfrom
Conversation
|
🚅 Deployed to the rivet-pr-4246 environment in rivet-frontend
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR Review: chore: get docker compose working againSummaryThis PR fixes several issues in the Docker development environment: Prometheus query syntax, Grafana dashboard metrics, Vector HTTP integration removal from engine config, and runner startup configuration. Overall the changes are well-targeted and correct, but there is one notable inconsistency to address. IssuesMissing docker-compose.yml regenerationThe template # Current state in docker-compose.yml (missing the new vars)
runner:
environment:
- RIVET_ENDPOINT=http://rivet-engine:6420
- RIVET_RUNNER_TOTAL_SLOTS=1000000Per CLAUDE.md: the Positive ChangesPrometheus label_values() syntax fixAll dashboards correctly move from the deprecated bare-label form to the metric-anchored form: This is required for newer Prometheus versions and prevents spurious "no data" in dashboard variables. Gasoline dashboard deduplication logicThe new PromQL join pattern using Pegboard dashboard legend format fix
Vector HTTP removalThe removal of New dispatch rate panels in gasoline dashboardReplacing the "Last Pull Workflows Duration" panels with stacked "Workflows Dispatched/s" panels provides more actionable throughput visibility. The separation between dispatches originating from workflows vs. non-workflow sources is a useful distinction. Minor Notes
🤖 Generated with Claude Code |
a4fe6de to
754e84e
Compare
121bf70 to
3da1f9e
Compare

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: