CodeSampleX

Recordscargotokio-macros2.7.2tokio_macros::main

Change the conditions
Fixed
Symboltokio_macros::main Package managercargo 1
Filter OSubuntu glibc Package version2.7.2 Architecturex64 libcglibc Clear filters

Current conditions

tokio_macros::main @2.7.2ubuntu glibc · x64 · cargo 1

4 of 7 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
4 / 7
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

2.7.2

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0479254218ac3780b34745e946705b5f6ea072bc45cc7771f5a9b6fbfb5955e8

View exact conditions View failure cluster
Library Version Health Measured there Projects
syn 3.0.3 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
syn 3.0.5 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
proc-macro2 1.0.107 PASS All observations passed contract passed 12 project-days
quote 1.0.47 PASS All observations passed contract passed 12 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.

Library2.7.22.5.0
syn 3.0.5 2.0.119
proc-macro2 1.0.107 1.0.107
quote 1.0.47 1.0.47

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