Bug Description
When I follow the the business path of budget exhausted, found that:
L818 set:
_turn_exit_reason = "budget_exhausted"
and then break the while loop.
but after the while loop, the "_turn_exit_reason" is covered:
_turn_exit_reason = f"max_iterations_reached({api_call_count}/{agent.max_iterations})"
so L818 is redundant.
Steps to Reproduce
- run out of iterations.
- "budget_exhausted" will never show in the fail message.
Expected Behavior
Remove the redundant line:
_turn_exit_reason = "budget_exhausted".
Actual Behavior
"budget_exhausted" will never show in the fail message.
Affected Component
Agent Core (conversation loop, context compression, memory)
Messaging Platform (if gateway-related)
No response
Debug Report
Operating System
Win10 + WSL2
Python Version
No response
Hermes Version
No response
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
When I follow the the business path of budget exhausted, found that:
L818 set:
_turn_exit_reason = "budget_exhausted"
and then break the while loop.
but after the while loop, the "_turn_exit_reason" is covered:
_turn_exit_reason = f"max_iterations_reached({api_call_count}/{agent.max_iterations})"
so L818 is redundant.
Steps to Reproduce
Expected Behavior
Remove the redundant line:
_turn_exit_reason = "budget_exhausted".
Actual Behavior
"budget_exhausted" will never show in the fail message.
Affected Component
Agent Core (conversation loop, context compression, memory)
Messaging Platform (if gateway-related)
No response
Debug Report
.Operating System
Win10 + WSL2
Python Version
No response
Hermes Version
No response
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?