Records/pypi/urllib3/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 2.7.0 FAIL
• 2.6.3 PASS 1 passing observations

Where it reproduced

• os=windows · runtime=python@3.10 ×4 2026-08-25 → 2026-08-26

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 2.6.3 → first failing release 2.7.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No resolved dependency tree for 2.6.3 or for 2.7.0, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• urllib3 2.7.0: util 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. HOWurllib3.util MIT-0 · 2026-09-06
• urllib3 2.7.0: exceptions.HTTPError 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. HOWurllib3.exceptions.HTTPError MIT-0 · 2026-09-06
• urllib3 2.7.0: exceptions.URLSchemeUnknown 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. HOWurllib3.exceptions.URLSchemeUnknown MIT-0 · 2026-09-06