standard-tests: Fix ToolsIntegrationTests to correctly handle "content_and_artifact" tools #29391
+43
−19
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.
Description:
The response from
tool.invoke()
is always a ToolMessage, with content and artifact fields, not a tuple.The tuple is converted to a ToolMessage here
langchain/libs/core/langchain_core/tools/base.py
Line 726 in b6ae7ca
Issue:
Currently
ToolsIntegrationTests
requiresinvoke()
to return a tuple and so standard tests fail for "content_and_artifact" tools. This fixes that to check the returned ToolMessage.This PR also adds a test that now passes.