CodeSampleX

Recordsgolanggithub.com/prometheus/commonfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

FAIL: unexpected serialized text output: # HELP http_requests_total Total HTTP requests. · # TYPE http_requests_total counter …

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-21 · Last seen: 2026-10-21

sha256:30d68f3de683…

github.com/prometheus/common/expfmt.DecodeOptions github.com/prometheus/common/expfmt.ExtractSamples github.com/prometheus/common/expfmt.MetricFamilyToText github.com/prometheus/common/expfmt.TextParser github.com/prometheus/common/model.IsValidMetricName github.com/prometheus/common/model.LabelName github.com/prometheus/common/model.Metric github.com/prometheus/common/model.MetricNameLabel github.com/prometheus/common/model.ParseDuration github.com/prometheus/common/model.Time

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.

Moved: 7 · unchanged at every release: 9

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