CodeSampleX

Recordsgolanggithub.com/prometheus/commonfailure issue

Failure signature

UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1

node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: should produce 4 tokens before eof for <str>

Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-05 · Last seen: 2026-09-05

sha256:b820b4edc1a5…

github.com/prometheus/common/expfmt.FmtOpenMetrics_1_0_0 github.com/prometheus/common/expfmt.FmtText github.com/prometheus/common/expfmt.Format github.com/prometheus/common/expfmt.Negotiate github.com/prometheus/common/expfmt.NegotiateAccept github.com/prometheus/common/expfmt.NewDecoder github.com/prometheus/common/expfmt.NewFormat github.com/prometheus/common/expfmt.NewTextParser github.com/prometheus/common/expfmt.TypeOpenMetrics github.com/prometheus/common/expfmt.TypeTextPlain github.com/prometheus/common/model.LegacyValidation

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: 4 · 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