[Bugfix]Capture stderr for python tool with uv as backend #182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@heheda12345 @dkundel-openai pls review |
5 tasks
Signed-off-by: wuhang <wuhang6@huawei.com>
wuhang2014
force-pushed
the
uvpythontool
branch
from
f3b1969 to
54a2f74
Compare
dkundel-openai
approved these changes
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When using uv as python execution backend, we only capture stdout for output. But there are errors in python code generated by gpt-oss sometimes. We should capture error message from stderr channel of subprocess as output of python tool.