Recordsnpmp-tryfailure issue
Failure signature
UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×4
node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-09-14
sha256:986d98189e70…
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
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×3 2026-08-31 → 2026-08-31
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-14 → 2026-09-14
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.
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- p-try 2.2.0: default This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWp-try.default MIT-0 · 2026-09-06
- p-try 2.2.0: pTry This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpTrynode 22.23.2 MIT-0 · 2026-08-27