Recordsgolanggo.opentelemetry.io/otel/metricv1.43.0
Change the conditions
Current conditions
go.opentelemetry.io/otel/metric @v1.43.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 4 / 4
- Contract verifications
- 0 / 1
- Usage records
- 8
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | contract passed | 25 project-days |
| go.opentelemetry.io/otel | v1.43.0 | contract passed | 27 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.43.0 | v1.24.0 |
|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.8.4 |
| go.opentelemetry.io/otel | v1.43.0 | v1.24.0 |
Moved: 2 · unchanged at every release: 0
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
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.43.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate