CodeSampleX

Recordsgolanggithub.com/google/pprofv0.0.0-20231212022811-ec68065c825egithub.com/google/pprof/profile.Location

Change the conditions
Fixed
OSlinux Package versionv0.0.0-20231212022811-ec68065c825e Symbolgithub.com/google/pprof/profile.Location
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/google/pprof/profile.Location @v0.0.0-20231212022811-ec68065c825elinux · glibc · x64 · go 1.26 · go 1

2 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Unknown 1 · Steady 0

First observed break

v0.0.0-20231212022811-ec68065c825e

linux · go@1.26

1 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
github.com/chzyer/readline v1.5.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/ianlancetaylor/demangle v0.0.0-20230524184225-eabc099b10ab CANDIDATE Correlated change; unproven combination builds observed 3 project-days
github.com/chromedp/chromedp v0.9.2 UNKNOWN No linked outcome measured nothing measured 3 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.

Moved: 2 · unchanged at every release: 1

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