Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
contract failed: unexpected primary DSN config fields · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-11-03 · Last seen: 2026-11-03
sha256:d23f7f4e9044…
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.0.0-20190605123033-f99c8df09eb5 not measured
- v0.0.0-20190510104115-cbcb75029529 not measured
- v0.0.0-20190426145343-a29dc8fdc734 not measured
- v0.0.0-20190411191339-88737f569e3a FAIL
- v0.0.0-20190313024323-a1f597ede03a not measured
- v0.0.0-20190308221718-c2843e01d9a2 not measured
- v0.0.0-20181029021203-45a5f77698d3 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-11-03 → 2026-11-03
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.0.0-20190605123033-f99c8df09eb5 | v0.0.0-20190510104115-cbcb75029529 | v0.0.0-20190426145343-a29dc8fdc734 | v0.0.0-20190411191339-88737f569e3a | v0.0.0-20190313024323-a1f597ede03a | v0.0.0-20190308221718-c2843e01d9a2 |
|---|---|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 | — | — | — |
| golang.org/x/sys | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d | v0.0.0-20190403152447-81d4e9dc473e | v0.0.0-20190316082340-a2f829d7f35f | v0.0.0-20190826190057-c7b8b68b1456 |
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: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.