CodeSampleX

Recordscargotokio1.43.0tokio::runtime::Builder::worker_threads

Change the conditions
Fixed
Package version1.43.0 Symboltokio::runtime::Builder::worker_threads
Filter OSalpine musl Runtimerust 1 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

tokio::runtime::Builder::worker_threads @1.43.0alpine musl · x64 · rust 1 · cargo · rust

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations
0 / 1
Contract verifications
1 / 2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 4

First observed break

1.43.0

linux · rust@1 · executionContext=rust

2 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
mio 1.2.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
socket2 0.5.10 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
tokio-macros 2.5.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
windows-sys 0.52.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
backtrace 0.3.76 PASS All observations passed contract passed 5 project-days
bytes 1.12.1 PASS All observations passed contract passed 1 project-day
libc 0.2.189 PASS All observations passed contract passed 1 project-day
pin-project-lite 0.2.17 PASS All observations passed contract passed 5 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.

Library1.53.11.43.0
mio 1.2.3 1.2.2
socket2 0.6.5 0.5.10
tokio-macros 2.7.2 2.5.0
windows-sys 0.61.2 0.52.0
backtrace — 0.3.76
bytes 1.12.1 1.12.1
libc 0.2.189 0.2.189
pin-project-lite 0.2.17 0.2.17

Moved: 4 · 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