Recordscargosynfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×2
error: could not compile `sample-axum-macros-debug-handler` (lib) due to 2 previous errors; 2 warnings emitted
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-11-17 · Last seen: 2026-11-17
sha256:b0b78cd39ba8…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 3.0.10 FAIL
- 3.0.9 PASS 4 passing observations
- 3.0.7 not measured
- 3.0.6 PASS 17 passing observations
- 3.0.5 PASS 7 passing observations
- 3.0.3 PASS 2 passing observations
- 2.0.119 FAIL
Where it reproduced
- os=linux ×2 2026-11-17 → 2026-11-17
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 failing release 2.0.119 → first passing release 3.0.3
What differs across the boundary
- unicode-ident 1.0.24, 1.0.25, 1.0.26 → 1.0.24, 1.0.25, 1.0.26, 1.0.27 evidence
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 passing release 3.0.9 → first failing release 3.0.10
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.0.10 | 3.0.9 | 3.0.7 | 3.0.6 | 3.0.5 | 3.0.3 | 2.0.119 |
|---|---|---|---|---|---|---|---|
| unicode-ident | 1.0.27 | 1.0.27 | 1.0.26 | 1.0.25 | 1.0.25 | 1.0.26 | 1.0.25 |
| proc-macro2 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 |
| quote | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 |
Moved: 1 · 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_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- syn 2.0.119: syn 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. HOWsyn MIT-0 · 2026-09-17
- syn 2.0.119 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. HOW MIT-0 · 2026-09-14