Avoid unwanted exception chaining when running async tool in sync context #9092
+4
−1
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.
Running async tool under sync context (require
settings.allow_tool_async_sync_conversion) is handled byTool._run_async_in_sync. If there's no running event loop, we used to run the coroutine directly when handling theRuntimeErrorraised byasyncio.get_running_loop(). This resulted in exception chaining, where the error raised by the tool will be chained with theRuntimeErrorraised byasyncio. Since the result will be passed to the LM as tool call result, such behavior is regarded as unnecessary leak of implementation detail, and will diverge the result of running withasyncand in sync. Move the real call outside of theexceptblock will resolve the problem.Before
After