Recordscargochronofailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-08 · Last seen: 2026-09-08
chrono::DateTime chrono::Duration chrono::NaiveDate chrono::NaiveDateTime chrono::NaiveTime chrono::Utc
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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
- executionContext=rust · os=linux · runtime=rust@1 ×1 2026-09-08 → 2026-09-08
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.4.42 → first failing release 0.4.45
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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.4.45 | 0.4.39 |
|---|---|---|
| android-tzdata | — | 0.1.1 |
| iana-time-zone | — | 0.1.65 |
| js-sys | — | 0.3.104 |
| num-traits | 0.2.19 | 0.2.19 |
| serde | 1.0.229 | — |
| serde_json | 1.0.151 | — |
| wasm-bindgen | — | 0.2.127 |
| windows-targets | — | 0.52.6 |
Moved: 0 · unchanged at every release: 8
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.
- No resolved dependency tree for 0.4.42 or for 0.4.45, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- chrono 0.4.45: Disabling chrono default features strips Utc::now and Local which require the clock feature rather than std, while serde support requires an explicit opt-in serde feature and serializes DateTime as an RFC 3339 string 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. HOWchrono::DateTimechrono::Utcchrono::NaiveDatechrono::NaiveTimechrono::NaiveDateTimechrono::Durationrust MIT-0 · 2026-08-15
- chrono 0.4.45: Build and add to dates with chrono 0.4 without the deprecated constructors, and know when month arithmetic clamps 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. HOWDateTime::from_timestampNaiveDate::from_ymd_optNaiveDateTime::and_utcNaiveDate::checked_add_monthsrust 1 MIT-0 · 2026-08-14