chore: release main - #499
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
…in span data (#469) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Nitesh Dhanpal <NiteshDhanpal@users.noreply.github.com> Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
Comment thread
src/agentex/lib/core/tracing/lineage.py
| refs.extend(entry.resolver(arguments or {})) | ||
| except Exception: | ||
| logger.warning("data-source resolver for tool %s failed; static refs kept", tool_name, exc_info=True) | ||
| return _dedupe(refs) |
Copy link
Copy Markdown
There was a problem hiding this comment.
Resolver output escapes fail-open guard
A custom resolver that returns a malformed reference reaches _dedupe outside the exception handler, where the unconditional model_dump call raises and propagates through provider completion. This violates lineage's fail-open contract and can turn an otherwise successful agent run into a failure.
Knowledge Base Used: Runtime tracing and observability
Prompt To Fix With AIThis is a comment left during a code review.
Path: src/agentex/lib/core/tracing/lineage.py
Line: 117
Comment:
**Resolver output escapes fail-open guard**
A custom resolver that returns a malformed reference reaches `_dedupe` outside the exception handler, where the unconditional `model_dump` call raises and propagates through provider completion. This violates lineage's fail-open contract and can turn an otherwise successful agent run into a failure.
**Knowledge Base Used:** [Runtime tracing and observability](https://app.greptile.com/scale-ai/-/custom-context/knowledge-base/scaleapi/scale-agentex-python/-/docs/runtime-tracing-and-observability.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Sorry, something went wrong.
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
Reviewers
At least 1 approving review is required to merge this pull request.
1 participant
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.
✨ Stainless prepared a new release
agentex-client: 0.25.00.25.0 (2026-08-24)
Full Changelog: agentex-client-v0.24.0...agentex-client-v0.25.0
Features
- lineage: capture tool data-source refs and agent build version in span data (#469) (941bbc4)
agentex-sdk: 0.25.00.25.0 (2026-08-24)
Full Changelog: agentex-sdk-v0.24.0...agentex-sdk-v0.25.0
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Greptile Summary
The release updates both distributions to 0.25.0 and adds lineage metadata for registered tool data sources plus agent build versions.
Confidence Score: 4/5
The PR appears safe to merge, with a non-blocking robustness issue in handling malformed custom lineage resolver output.
The normal lineage, packaging, and version-stamping paths are coherent, but resolver return values are processed outside the documented fail-open guard and can propagate an exception from provider completion.
Files Needing Attention: src/agentex/lib/core/tracing/lineage.py
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart LR A[Tool registration] --> B[Data-source refs and resolver] C[Tool or provider execution] --> D[Serialized function-call items] B --> E[Lineage resolution] D --> E E --> F[Merge sgp.lineage.refs into span data] G[AGENT_VERSION environment value] --> H[SGP processor enrichment] F --> I[Completed business span] H --> I I --> J[SGP export]
Prompt To Fix All With AIReviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile
Context used (4)