Recordsgolanggithub.com/prometheus/client_modelfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
Traceback (most recent call last): · File <str>, line 7, in <module> · File <str>, line 17, in initialize · raise RuntimeError(
Evidence quality: complete · unclassified-diagnostic · gap stage-unknown · First recorded: 2026-08-27 · Last seen: 2026-08-27
sha256:1d79a47b3888…
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.
- v0.6.2 not measured
- v0.6.1 not measured
- v0.5.0 not measured
- v0.2.0 FAIL
- v0.0.0-20190812154241-14fe0d1b01d4 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-27 → 2026-08-27
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.
| Library | v0.6.2 | v0.6.1 | v0.5.0 | v0.2.0 | v0.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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/prometheus/client_model v0.2.0: go.Summary This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/prometheus/client_model/go.Summary MIT-0 · 2026-09-01
- github.com/prometheus/client_model v0.2.0: go.Histogram This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/prometheus/client_model/go.Histogram MIT-0 · 2026-09-01
- github.com/prometheus/client_model v0.2.0: go.Gauge This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/prometheus/client_model/go.Gaugego MIT-0 · 2026-08-28