Recordscargowasm-bindgen-macro-supportfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0599 ×1
error[E0599]: no method named `into_node` found for struct `wasm_bindgen_macro_support::error::Diagnostic` in the current scope
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-10-17 · Last seen: 2026-10-17
sha256:eaa7d8163513…
wasm_bindgen_macro_support::expand_class_marker
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.
- 0.2.130 not measured
- 0.2.129 PASS 1 passing observations
- 0.2.128 FAIL
- 0.2.127 PASS 6 passing observations
Where it reproduced
- os=linux ×1 2026-10-17 → 2026-10-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 passing release 0.2.127 → first failing release 0.2.128
What differs across the boundary
- syn 2.0.119 → 3.0.6, 3.0.9 hypothesis
- wasm-bindgen-shared 0.2.127 → 0.2.128 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 0.2.128 → first passing release 0.2.129
What differs across the boundary
- syn 3.0.9 → 3.0.6, 3.0.9 hypothesis
- wasm-bindgen-shared 0.2.129 → 0.2.128 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.
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 | 0.2.130 | 0.2.129 | 0.2.128 | 0.2.127 |
|---|---|---|---|---|
| bumpalo | 3.20.4 | 3.20.3 | 3.20.3 | 3.20.3 |
| syn | 3.0.10 | 3.0.9 | 3.0.6 | 2.0.119 |
| wasm-bindgen-shared | 0.2.130 | 0.2.129 | 0.2.128 | 0.2.127 |
| proc-macro2 | 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 |
Moved: 3 · 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
- wasm-bindgen-macro-support 0.2.128: expand 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. HOWexpand MIT-0 · 2026-10-18
- wasm-bindgen-macro-support 0.2.128: expand_struct_marker 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. HOWexpand_struct_marker MIT-0 · 2026-10-17
- wasm-bindgen-macro-support 0.2.128: expand_class_marker 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. HOWexpand_class_marker MIT-0 · 2026-10-17