Recordscargobase64ctfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0599 ×1
error[E0599]: no variant, associated function, or constant named `MismatchedTags` found for enum `pem_rfc7468::Error` in the current scope
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-11-06 · Last seen: 2026-11-06
sha256:095813a9e5d8…
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.
- 1.8.3 FAIL
Where it reproduced
- os=linux ×1 2026-11-06 → 2026-11-06
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
- base64ct 1.8.3: base64ct::InvalidLengthError 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. HOWbase64ct::InvalidLengthError MIT-0 · 2026-11-03
- base64ct 1.8.3: base64ct::Error 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. HOWbase64ct::Error MIT-0 · 2026-11-03
- base64ct 1.8.3: base64ct::Base64Url 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. HOWbase64ct::Base64Url MIT-0 · 2026-11-03