mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-04-25 00:51:20 +00:00
fix: always log outer loop exception traceback at DEBUG level
Replace the verbose_logging-gated logging.exception() with an unconditional logger.debug(exc_info=True). The full traceback now always lands in agent.log when debug logging is enabled, without requiring the verbose_logging flag or spamming the console. Previously, production errors in the 700-line response processing block (normalization, tool dispatch, final response handling) were logged as one-line messages with the traceback hidden behind verbose_logging — making post-mortem debugging difficult.
This commit is contained in:
parent
289d2745af
commit
08f35076c9
1 changed files with 1 additions and 2 deletions
|
|
@ -9988,8 +9988,7 @@ class AIAgent:
|
|||
except (OSError, ValueError):
|
||||
logger.error(error_msg)
|
||||
|
||||
if self.verbose_logging:
|
||||
logging.exception("Detailed error information:")
|
||||
logger.debug("Outer loop error in API call #%d", api_call_count, exc_info=True)
|
||||
|
||||
# If an assistant message with tool_calls was already appended,
|
||||
# the API expects a role="tool" result for every tool_call_id.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue