Recordscargoanyhow1.0.104anyhow::Error::backtrace
Published samples
- anyhow 1.0.104: RUST_LIB_BACKTRACE overrides RUST_BACKTRACE during eager anyhow backtrace capture, and Debug formatting appends stack traces only when Captured 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. HOWanyhow::Error::backtracestd::backtrace::Backtrace::statusstd::backtrace::BacktraceStatusanyhow::bailanyhow::Context::contextrust MIT-0 · 2026-08-16
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| rust 1 · Rust · cargo · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
No failure clusters observed.