CodeSampleX

Sample

Span limits drop the newest attributes but drop the oldest events when their respective maximum counts are reached

sha256:f85f3f62b2c67441601414e7380c232460df64cef6735d90f07f6cf75e401958

PUBLISHED L3_CONTRACT_PASS MIT-0

Execution evidence

Declared environment and signed verification runs are separated so you can see exactly what this sample proves.

Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS

Declared environment

Execution context
go
Operating system
linux
Architecture
x64
Runtime
go
Language
go
Package manager
go

Verification-run environments

Execution context
go 1.26
Operating system
linux alpine · musl
Architecture
x64
Runtime
go 1.26
Language
go
Package manager
go
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17

Case

Goal
Span limits drop the newest attributes but drop the oldest events when their respective maximum counts are reached HOW
Packages
go.opentelemetry.io/otel/sdk v1.45.0
Environment
go
Created
2026-08-17T06:47:26Z

Commonly assumed

Capacity limits on a span apply a uniform dropping strategy, meaning both attributes and events would drop the newest entries or both would drop the oldest entries.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts