Skip to content

about DefaultToolCallingManager support toolcall chunk in stream mode #5732

@Iristack

Description

@Iristack

It looks like DefaultToolCallingManager isn't handling tool call chunks properly right now.
It throws an:

IllegalArgumentException complaining that the toolName is null or empty.

Here is what I'm seeing:

0 = {AssistantMessage$ToolCall@6413} "ToolCall[id=call_c37e074f0d3846d091cdf85e, type=function, name=echo, arguments=]"
1 = {AssistantMessage$ToolCall@6443} "ToolCall[id=call_c37e074f0d3846d091cdf85e, type=function, name=, arguments={"text": "2"}]"

maybe we can support it?


For anything other than bug reports and feature requests (performance, refactoring, etc),
just go ahead and file the issue. Please provide as many details as possible.

If you have a question or a support request, please open a new discussion on GitHub Discussions
or ask a question on StackOverflow.

Please do not create issues on the Issue Tracker for questions or support requests.
We would like to keep the issue tracker exclusively for bug reports and feature requests.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions