CodeSampleX

Recordsgolanggithub.com/prometheus/client_modelfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

<path> · <path>

Evidence quality: complete · unclassified-diagnostic · gap stage-unknown · First recorded: 2026-08-27 · Last seen: 2026-08-27

sha256:13e610412b4d…

github.com/prometheus/client_model/go.Counter github.com/prometheus/client_model/go.Gauge github.com/prometheus/client_model/go.LabelPair github.com/prometheus/client_model/go.Metric github.com/prometheus/client_model/go.MetricFamily github.com/prometheus/client_model/go.MetricType github.com/prometheus/client_model/go.MetricType_COUNTER github.com/prometheus/client_model/go.MetricType_GAUGE

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN 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.

Libraryv0.6.2v0.6.1v0.5.0v0.2.0v0.0.0-20190812154241-14fe0d1b01d4
github.com/golang/protobuf — — — v1.5.4 v1.3.5
google.golang.org/protobuf v1.36.6 v1.36.12 v1.35.1 — —

Moved: 2 · unchanged at every release: 0

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