You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ad9e703
Browse filesBrowse the repository at this point in the historyBrowse files
fix(webapp,run-store): make run-ops sharding failures visible and unroutable ids a 404
Four QA findings from the N-way run-ops sharding pass:
- A replication source whose publication carries no tables replicated nothing
while boot passed and the service looked healthy. The client now emits a typed
PublicationMisconfiguredError and the webapp counts it per source
(runs_replication_publication_misconfigured_total), so it is alarmable.
- POST /api/v1/waitpoints/tokens/:id/complete (and the HTTP-callback route)
answered 500 for an id naming an unconfigured shard; both now answer 404 like
the run routes.
- An unparseable runOpsMintShardSet still degrades to gen-1 minting, but the
parse failure is now reported through the caller's logger instead of vanishing.
- Per-shard observability: runops_shard_routed_total{shard} from the router and
runops_read_through_source_total{source,shard} from the read-through layer.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments