Summary

On macOS arm64, instrument_telemetry(tracer=...) accepts an OpenTelemetry tracer, but a Monty checkout and run emit no session or run spans. I reproduced this with the 1.0.0 macOS arm64 wheel. I previously observed the same behavior with the 0.0.23 macOS arm64 wheel, while the 0.0.23 Linux wheel emitted session and run spans.

Reproduction

from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
from opentelemetry.sdk.trace.export.in_memory_span_exporter import InMemorySpanExporter
from pydantic_monty import Monty, instrument_telemetry

provider = TracerProvider()
exporter = InMemorySpanExporter()
provider.add_span_processor(SimpleSpanProcessor(exporter))
instrument_telemetry(tracer=provider.get_tracer("monty-repro"))

with Monty() as pool:
    with pool.checkout(script_name="repro.py") as session:
        print("result:", session.feed_run("1 + 2"))

print("spans:", [span.name for span in exporter.get_finished_spans()])

On macOS arm64 with pydantic-monty 1.0.0, this prints:

result: 3
spans: []

Expected: session and run spans, as observed with the 0.0.23 Linux wheel.

Environment: macOS arm64, CPython 3.14.7, pydantic-monty 1.0.0. The script uses Monty's telemetry API directly, without Logfire.

Activity

No activity yet.