Recordscargotracing0.1.41tracing
Change the conditions
Current conditions
tracing @0.1.41alpine musl · x64 · rust 1 · cargo · rust
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-11-11
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.1.41
linux
3 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:bc14a039ced7e283a0e0b777d06d2254b5f95b21a42ddbc66be7a9652e7086c0
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pin-project-lite | 0.2.17 | PASS All observations passed | contract passed | 34 project-days |
| tracing-attributes | 0.1.31 | PASS All observations passed | contract passed | 32 project-days |
| tracing-core | 0.1.36 | PASS All observations passed | contract passed | 34 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.1.44 | 0.1.41 |
|---|---|---|
| log | 0.4.34 | — |
| pin-project-lite | 0.2.17 | 0.2.17 |
| tracing-attributes | 0.1.31 | 0.1.31 |
| tracing-core | 0.1.36 | 0.1.36 |
Moved: 0 · unchanged at every release: 4
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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0277 ×3 0.1.41 os=linux sha256:bc14a039ced7…error[E0277]: the trait bound `[(&tracing::field::Field, Option<&dyn Value>)]: tracing_core::field::private::ValidLen<'_>` is not satisfied …rust/rustc · compiler-diagnostic · outer cargo build, cargo run, cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_TEST exit 101 ×3 0.1.41 os=linux sha256:4f232600c5a8…error: test failed, to rerun pass `--test contract` · running 0 tests …rust/test · test-runner-diagnostic · outer cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 E0425 ×2 0.1.41 os=linux sha256:4bcb4519e22e…error[E0425]: cannot find value `__CALLSITE` in this scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-03 · Last seen: 2026-11-03
-
observed PROJECT_COMPILE exit 101 ×2 0.1.41 os=linux sha256:4c786cbbce8a…error: could not compile `sample` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-03
-
observed PROJECT_COMPILE exit 101 E0603 ×2 0.1.41 os=linux sha256:ad49b0c381f1…error[E0603]: struct `Interest` is privaterust/rustc · compiler-diagnostic · outer cargo run, cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 E0599 ×1 0.1.41 os=linux sha256:21e1af4105bd…error[E0599]: no method named `metadata` found for struct `DefaultCallsite` in the current scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-03 · Last seen: 2026-11-03
-
observed PROJECT_COMPILE exit 101 E0277 ×1 0.1.41 os=linux sha256:235816106726…error[E0277]: the trait bound `Level: Default` is not satisfiedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-01 · Last seen: 2026-11-01
-
observed PROJECT_COMPILE exit 101 E0599 ×1 0.1.41 os=linux sha256:2363542ad75a…error[E0599]: no associated function or constant named `MAX` found for struct `Level` in the current scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 ×1 0.1.41 os=linux sha256:3495fda0b622…error: could not compile `tracing-field-sample` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 ×1 0.1.41 os=linux sha256:3c7d21b0f73a…error: could not compile `sample-tracing-metadata` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 E0521 ×1 0.1.41 os=linux sha256:631a933414e7…error[E0521]: borrowed data escapes outside of methodrust/rustc · compiler-diagnostic · outer cargo testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-02 · Last seen: 2026-11-02
-
observed PROJECT_COMPILE exit 101 ×1 0.1.41 os=linux sha256:7f293f2497c1…error: could not compile `sample` (bin <str>) due to 2 previous errors; 1 warning emittedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-03 · Last seen: 2026-11-03
Showing the 12 most-reported of 26 recorded failure clusters. The rest are single reports.