Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
# github.com/nats-io/nats-server/v2/logger · open <path>: no such file or directory · # github.com/nats-io/nats-<token> …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-24 · Last seen: 2026-10-24
sha256:a50c29a5b765…
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-20191011191535-87dc89f01550 not measured
- v0.0.0-20191002192127-34f69633bfdc not measured
- v0.0.0-20190820162420-60c769a6c586 not measured
- v0.0.0-20190701094942-4def268fd1a4 FAIL
- v0.0.0-20190605123033-f99c8df09eb5 not measured
- v0.0.0-20190510104115-cbcb75029529 not measured
- v0.0.0-20190426145343-a29dc8fdc734 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-24 → 2026-10-24
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-20191011191535-87dc89f01550 | v0.0.0-20191002192127-34f69633bfdc | v0.0.0-20190820162420-60c769a6c586 | v0.0.0-20190701094942-4def268fd1a4 | v0.0.0-20190605123033-f99c8df09eb5 | v0.0.0-20190510104115-cbcb75029529 | v0.0.0-20190426145343-a29dc8fdc734 |
|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20200520182314-0ba52f642ac2 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190813141303-74dc4d7220e7 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 |
| golang.org/x/sys | v0.0.0-20200523222454-059865788121 | v0.0.0-20190412213103-97732733099d | v0.0.0-20220722155257-8c9f86f7a55f | v0.0.0-20190726091711-fc99dfbffb4e | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d |
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.