CodeSampleX

Recordsgolanggolang.org/x/cryptofailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

# example.com/sample/test · test/contract.go:<n>:<n>: logrus.PanicLevel.MarshalText undefined (type logrus.Level has no field or method MarshalText)

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

sha256:f0678a2e2b48…

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.0.0-20190313024323-a1f597ede03av0.0.0-20190308221718-c2843e01d9a2v0.0.0-20180904163835-0709b304e793
golang.org/x/sys v0.0.0-20190316082340-a2f829d7f35f v0.0.0-20190826190057-c7b8b68b1456 —

Moved: 1 · 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