fix(instrumentation-py): repair Mirascope, Mistral, and Ollama OTel 2.x spans - #385
Merged
fran3cc merged 1 commit intoAug 21, 2026
Conversation
Nightingalelyy
marked this pull request as ready for review
August 19, 2026 15:59
Contributor
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
focused package tests: Mirascope 30/30, Mistral 18/18, Ollama 16/16 (64/64)
all three wheels build successfully
release inventory, release intent, Ruff format/check, Python compilation, and diff checks pass
exact example marker: otel2-fix-py-group-19-20260817T152514Z
complete example processes: 18/18
The exact marker returned 19 traces and 42 records. Every tree and full record was inspected: one root per trace, matching list/tree/detail sets, exact parent links, 42 unique record IDs and 42 unique span IDs, meaningful bounded content, exact model/usage/stream data, connected tools, controlled failures, grouping, privacy, and no forbidden aliases.
Full source and paired-example diffs were audited against every applicable document under
contribution/; canonical span fields, OTel attribute shapes, release-intent/version ownership, and package boundaries have no remaining package-owned violation.External follow-ups
Companion examples