Repository navigation
fix(crewai): trace tools run by native function calling #292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pylaterreur
wants to merge
4
commits into
alibaba:main
Choose a base branch
from
pylaterreur:crewai-native-tool-spans
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7c1950b
fix(crewai): trace tools run by native function calling
pylaterreur f178a2f
Merge branch 'main' into crewai-native-tool-spans
pylaterreur 4d4d2b0
Merge remote-tracking branch 'origin/main' into crewai-native-tool-spans
pylaterreur 0a4aded
fix(crewai): keep native tool call ids and mark returned ToolFailures
pylaterreur File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handle structured tool failures. CrewAI supports returning a
ToolFailurewithout raising an exception. The new wrapper treats this as a successful return and marks the spanOK, even though the tool explicitly reported failure. Could we recognize this result, mark the spanERROR, and add a test covering a returnedToolFailure?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 0a4aded. A returned
ToolFailurenow ends the span with ERROR: the description isas_agent_message()anderror.typeisRuntimeError. This applies on the native path, and on the ReAct path throughToolUsage.last_failure, which reported OK before. Testing this also showed that a raw result JSON can't encode (aToolFailure, a pydantic model) made the handler raise before ending the span. The span now records the text the agent gets, as_usedoes. New tests cover both paths.🤖 Generated with Claude Code