Recordsgolanggo.uber.org/zap
there is a sample for this release and API (4)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
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.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.13.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:cc6da42c69d5a8040f6a9dbda27d7d8e0daef42f5c34d1da8e73713061384c8d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/stretchr/testify | v1.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.uber.org/multierr | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| go.uber.org/multierr | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| github.com/pkg/errors | v0.8.1 | PASS All observations passed | contract passed | 21 project-days |
| github.com/pkg/errors | v0.9.1 | PASS All observations passed | contract passed | 1 project-day |
| go.uber.org/atomic | v1.5.0 | PASS All observations passed | contract passed | 4 project-days |
| go.uber.org/atomic | v1.6.0 | PASS All observations passed | contract passed | 16 project-days |
| golang.org/x/lint | v0.0.0-20190930215403-16217165b5de | PASS All observations passed | contract passed | 20 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.
| Library | v1.28.0 | v1.27.1 | v1.27.0 | v1.26.0 | v1.13.0 |
|---|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.8.1 | v1.8.1 | v1.8.1 | v1.4.0 |
| go.uber.org/goleak | v1.3.0 | v1.3.0 | v1.3.0 | v1.2.0 | — |
| go.uber.org/multierr | v1.11.0 | v1.11.0 | v1.10.0 | v1.10.0 | v1.3.0 |
| github.com/pkg/errors | — | — | — | — | v0.9.1 |
| go.uber.org/atomic | — | — | — | — | v1.5.0 |
| go.yaml.in/yaml/v3 | v3.0.4 | — | — | — | — |
| golang.org/x/lint | — | — | — | — | v0.0.0-20190930215403-16217165b5de |
| gopkg.in/yaml.v3 | — | v3.0.1 | v3.0.1 | v3.0.1 | — |
Moved: 3 · unchanged at every release: 5
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.