Recordspypigreenletfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
E AssertionError: assert [{<str>...ss<str>stale'}] == [] · E · E Left contains 2 more items, first extra item: {<str>: <str>, <str>: [], <str>: <str>} …
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-08-26 · Last seen: 2026-08-26
sha256:169172038321…
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.
- 3.5.6 not measured
- 3.5.5 PASS 1 passing observations
- 3.5.4 FAIL
- 3.4.0 PASS 3 passing observations
- 3.2.4 PASS 1 passing observations
- 3.0.3 PASS 3 passing observations
Where it reproduced
- os=windows · runtime=python@3.10 ×1 2026-08-26 → 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 3.4.0 → first failing release 3.5.4
What differs across the boundary
- sqlalchemy 2.0.52 → — hypothesis
- typing-extensions 4.15.0 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 3.5.4 → first passing release 3.5.5
Both trees resolved every dependency to the same version. Nothing here moved.
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 | 3.5.6 | 3.5.5 | 3.5.4 | 3.4.0 | 3.0.3 |
|---|---|---|---|---|---|
| sqlalchemy | — | — | — | 2.0.52 | — |
| typing-extensions | — | — | — | 4.15.0 | — |
Moved: 0 · unchanged at every release: 2
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
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- greenlet 3.5.4: greenlet.parent 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. HOWgreenlet.greenlet.parentpython 3.12 MIT-0 · 2026-09-01
- greenlet 3.5.4: Observe greenlet switch and throw event dispatching via settrace and trace listener inspection with gettrace 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. HOWgreenlet.getcurrentgreenlet.gettracegreenlet.greenletgreenlet.settrace MIT-0 · 2026-08-28
- greenlet 3.5.4: Observe greenlet ContextVar context isolation, initial uninherited gr_context instantiation, and explicit context propagation semantics 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. HOWgreenlet.greenlet.gr_contextgreenlet.greenletpython MIT-0 · 2026-08-17