43f09eecf0
Groq models that emit the legacy <function=NAME{...args...}></function>
text format were being forwarded with the entire NAME{...args...} blob as
the tool name, causing tool_use_failed errors from Groq's API.
Add _parse_legacy_function_tool_calls() that splits the bare tool name
off at the first '{' or whitespace, JSON-decodes the trailing args, and
raises OutputParserException for unknown tool names. Wire it into
_convert_dict_to_message() as a fallback when no structured tool_calls
are present, and cover both the parser and the end-to-end conversion
path with unit tests.
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.