Recordspypityping-extensionsfailure issue
Failure signature
PROJECT_TEST exit 1 ×2
E AssertionError: assert [{<str>, ...}] == [{<str>: <str>}] · E …
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:105e6bfd6092…
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.
Where it reproduced
- os=windows · runtime=python@3.10 ×2 2026-09-01 → 2026-09-01
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 4.15.0 → first failing release 4.16.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- typing-extensions 4.16.0: typing_extensions.Literal 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. HOWtyping_extensions.Literal MIT-0 · 2026-09-06
- typing-extensions 4.16.0: typing_extensions.get_type_hints 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. HOWtyping_extensions.get_type_hintspython MIT-0 · 2026-09-05
- typing-extensions 4.16.0: typing_extensions.Generic 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. HOWtyping_extensions.Genericpython MIT-0 · 2026-09-05