CodeSampleX

Recordscargoblock-buffer0.10.4block_buffer::BlockBuffer

Change the conditions
Fixed
Symbolblock_buffer::BlockBuffer Package managercargo
Filter OSalpine musl Runtimerust 1 Package version0.10.4 Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

block_buffer::BlockBuffer @0.10.4alpine 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

Observed problems 1 · Steady 2

First observed break

0.10.4

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:82432d69f18bcc5c068ad19b42779cea4c94019603cf65549bad8147e3d5bf7a

Library Version Health Measured there Projects
generic-array 0.14.7 PASS All observations passed contract passed 13 project-days
generic-array 0.14.9 PASS All observations passed builds observed 2 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.

Library0.12.10.10.4
generic-array — 0.14.9
hybrid-array 0.4.15 —

Moved: 0 · unchanged at every release: 2

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

Showing the 12 most-reported of 14 recorded failure clusters. The rest are single reports.