CodeSampleX

Recordsgolanggithub.com/prometheus/client_golangfailure issue

Failure signature

PROJECT_COMPILE exit 1 Evidence gap ×4

Evidence quality: partial · go/compiler · build-aggregate · outer go test · gap diagnostic-missing · First recorded: 2026-08-31 · Last seen: 2026-09-08

sha256:c2ae6d87252c…

github.com/prometheus/client_golang/prometheus.CounterOpts github.com/prometheus/client_golang/prometheus.GaugeOpts github.com/prometheus/client_golang/prometheus.HistogramOpts github.com/prometheus/client_golang/prometheus.NewCounter github.com/prometheus/client_golang/prometheus.NewGauge github.com/prometheus/client_golang/prometheus.NewHistogram github.com/prometheus/client_golang/prometheus.NewRegistry github.com/prometheus/client_golang/prometheus.NewSummary github.com/prometheus/client_golang/prometheus.Registerer github.com/prometheus/client_golang/prometheus.SummaryOpts

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 9 · unchanged at every release: 5

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

Published answers for the affected releases

Back to the package