Skip to content

Conversation

@ejstuart
Copy link
Contributor

@ejstuart ejstuart commented Oct 29, 2025

Went with the example I posted in the issue's thread, this is to maintain the framework's error as properly propagated while not rethrowing exceptions defined by users in their tools.

@ejstuart ejstuart requested a review from a team as a code owner October 29, 2025 08:25
invokerClassName, methodCreateInfo.methodName(),
methodCreateInfo.argumentMapperClassName(), methodCreateInfo.executionModel(),
methodCreateInfo.returnBehavior());
methodCreateInfo.returnBehavior(), false);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this should be configurable, not just hardcoded to false. But that's something I can have a look at in a subsequent PR, so no worries.

@quarkus-bot
Copy link

quarkus-bot bot commented Oct 29, 2025

Status for workflow Build (on pull request)

This is the status report for running Build (on pull request) on commit 53b3c66.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@geoand geoand merged commit e13b511 into quarkiverse:main Oct 29, 2025
81 checks passed
@geoand
Copy link
Collaborator

geoand commented Dec 10, 2025

Heads up: I am going to align with upstream LangChain4j on error handling with #2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Throwing IllegalArgumentException from the tool breaks streaming response handler

3 participants