Recordscargofutures-core0.3.34
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
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 |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_COMPILE 2✓ 5✕ · PROJECT_PROCESS 2✓ — Usage: USED 2✓
|
ELEVATED FAILURE | 9 +2 | 0 | 44% | 1 | 2026-09-15 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 2✓
|
LOW | 4 +2 | 2 | 100% | 1 · 1✓ | 2026-09-17 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0277 ×1 0.3.34 os=linux futures_core sha256:079d54d4b2e3…error[E0277]: `T` cannot be unpinned · error[E0277]: `E` cannot be unpinnedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 E0596 ×1 0.3.34 os=linux futures_core sha256:543987e39480…error[E0596]: cannot borrow data in dereference of `Pin<&mut ReadyTryFuture<T, E>>` as mutablerust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 E0119 ×1 0.3.34 os=linux futures_core sha256:5fe0d0b2f0ce…error[E0119]: conflicting implementations of trait `TryFuture` for type `ReadyTryFuture<_, _>`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 ×1 0.3.34 os=linux futures_core sha256:8f6f2276b3f1…error: could not compile `sample-futures-core` (bin <str>) due to 2 previous errors; 1 warning emittedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 ×1 0.3.34 os=linux futures_core sha256:e3dee1f39a56…error: could not compile `sample-futures-core` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
Symbols
- futures_core 1 1 of 1 runs passed
Published samples
- futures-core 0.3.34 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. HOW MIT-0 · 2026-09-15