Recordscargowindows-linkfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0432 ×3
error[E0432]: unresolved import `windows_sys::Win32::Foundation::BOOL`
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo check, cargo run · First recorded: 2026-09-19 · Last seen: 2026-10-09
sha256:2743506d5093…
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.1 FAIL
Where it reproduced
- os=linux ×3 2026-09-19 → 2026-10-09
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- windows-link 0.2.1: windows_link::link 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. HOWwindows_link::link MIT-0 · 2026-09-15