[Server] Log expected tool failures at debug level - #433
Open
ousamabenyounes wants to merge 1 commit into
Open
Conversation
ousamabenyounes
requested review from
CodeWithKyrian,
Nyholm,
chr-hertel and
soyuka
as code owners
August 18, 2026 00:54
Expected tool failures are part of normal tool execution, so log them at debug severity while preserving error logging for unexpected exceptions.
ousamabenyounes
force-pushed
the
fix/issue-157
branch
from
August 18, 2026 13:44
c4529aa to
7ec3907
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
ToolCallExceptionfailures at debug severity instead of error severityFixes #157
Test verification (RED → GREEN)
Before the production change, the focused regression test failed with:
After the change:
Full local CI replay: