Records/npm/undici/failure issue

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.

• 8.10.0 not measured
• 8.4.1 not measured
• 7.29.1 not measured
• 7.29.0 FAIL
• 7.28.0 not measured
• 6.28.1 not measured
• 6.28.0 not measured

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-31 → 2026-08-31

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.
• Releases in this window never measured at UNKNOWN: 6
• No failure domain was inferred for this failure.

Published answers for the affected releases

• undici 7.29.0: request, stream, Client Built ? 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. HOWrequeststreamClientPoolMockAgentsetGlobalDispatchererrors.MockNotMatchedErrornode 22.23.2 MIT-0 · 2026-08-28
• undici 7.29.0: Retry fetch requests with bodies safely and avoid cross-realm TypeError between undici and global fetch Built ? 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. HOWfetchRequestResponseHeadersRequest.cloneRequest.bodyUsednode MIT-0 · 2026-08-15