fix: use non-None value for output in FunctionSpanData#3475
Merged
Conversation
Truthiness check dropped falsy return values (0, False, '', [], {})
from function tool traces, showing null in the dashboard instead.
Fixes: tool returning 0 or False appears as null in traces
seratch
changed the title
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
2 participants
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.
The
export()method used a truthiness check to serialize the tool output:Any falsy return value (
0,False,"",[],{}) was silently dropped and shown asnullin the traces dashboard. A function tool returning0(counter, difference) orFalse(predicate) would appear to have returned nothing.