refactor: update failure message handling in display module and add debug logging in code execution tool

- Modified the `_wrap` function to append a failure suffix without applying red coloring, simplifying the failure message format.
- Introduced temporary debug logging in the `execute_code` function to track enabled and sandbox tools, aiding in troubleshooting.
This commit is contained in:
teknium1
2026-02-24 14:25:27 -08:00
parent 99af12af3f
commit 6845852e82
2 changed files with 6 additions and 2 deletions

View File

@@ -310,10 +310,10 @@ def get_cute_tool_message(
return ("..." + p[-(n-3):]) if len(p) > n else p
def _wrap(line: str) -> str:
"""Apply red coloring and failure suffix when the tool failed."""
"""Append failure suffix when the tool failed."""
if not is_failure:
return line
return f"{_RED}{line}{failure_suffix}{_RESET}"
return f"{line}{failure_suffix}"
if tool_name == "web_search":
return _wrap(f"┊ 🔍 search {_trunc(args.get('query', ''), 42)} {dur}")

View File

@@ -342,6 +342,10 @@ def execute_code(
session_tools = set(enabled_tools) if enabled_tools else set()
sandbox_tools = frozenset(SANDBOX_ALLOWED_TOOLS & session_tools)
# Temporary debug — remove after investigating
with open("/tmp/hermes_exec_debug.log", "a") as _dbg:
_dbg.write(f"enabled_tools={enabled_tools}\nsandbox_tools={sandbox_tools}\n---\n")
if not sandbox_tools:
sandbox_tools = SANDBOX_ALLOWED_TOOLS