Recordsgolanggithub.com/rs/zerolog
there is a sample for this release and API (1)
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.15.0
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:d97bfab895bdfc36fdefb474c1cb805c7ce5462b0b8c078c36b8a82008810c4f
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/coreos/go-systemd | v0.0.0-20190321100706-95778dfbb74e | UNKNOWN No linked outcome measured | nothing measured | 8 project-days |
| github.com/coreos/go-systemd | v0.0.0-20190719114852-fd7a80b32e1f | UNKNOWN No linked outcome measured | nothing measured | 21 project-days |
| github.com/rs/xid | v1.2.1 | UNKNOWN No linked outcome measured | nothing measured | 27 project-days |
| github.com/zenazn/goji | v0.9.0 | UNKNOWN No linked outcome measured | nothing measured | 28 project-days |
| github.com/pkg/errors | v0.8.1 | PASS All observations passed | contract passed | 29 project-days |
| github.com/pkg/errors | v0.9.1 | PASS All observations passed | contract passed | 1 project-day |
| golang.org/x/tools | v0.0.0-20190425163242-31fd60d6bfdc | PASS All observations passed | builds observed | 8 project-days |
| golang.org/x/tools | v0.0.0-20190823170909-c4a336ef6a2f | PASS All observations passed | builds observed | 2 project-days |
| golang.org/x/tools | v0.0.0-20200103221440-774c71fcf114 | PASS All observations passed | builds observed | 7 project-days |
| golang.org/x/tools | v0.6.0 | PASS All observations passed | contract passed | 10 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.