Recordspypigreenletfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
Traceback (most recent call last): · File <str>, line 9, in <module> · from sqlalchemy import select · ModuleNotFoundError: No module named <str>
Evidence quality: complete · python3 · unclassified-diagnostic · outer python3 · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:03cd650ce90c…
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
- os=linux · runtime=python@3.12 ×1 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.
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 |
|---|---|---|---|---|
| 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
- 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: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.