You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I included a self-contained, minimal example that demonstrates the issue INCLUDING all the relevant imports. The code run AS IS to reproduce the issue.
[2025-01-18 14:04:35,940]-VIP-[supervisorProcess.py:97]: shell->supervisor
Starting tool: shell_tool with inputs: {'command': 'free -m'}
[2025-01-18 14:04:37,599]-INFO-[tools.py:24]: executing shell output: total used free shared buff/cache available
Mem: 32064 1077 31083 3 298 30986
Swap: 8192 0 8192
Done tool: shell_tool
The memory usage is as follows:
- Total memory: 32064 MB
- Used memory: 1077 MB
- Free memory: 31083 MB
- Shared memory: 3 MB
- Buffer/cache memory: 298 MB
- Available memory: 30986 MB
The swap memory usage is as follows:
- Total swap: 8192 MB
- Used swap: 0 MB
- Free swap: 8192 MB[2025-01-18 14:04:40,450]-VIP-[agentSupervisor.py:41]: {'next': 'shell'}
[2025-01-18 14:04:40,504]-VIP-[supervisorProcess.py:97]: shell->supervisor
[2025-01-18 14:04:41,771]-INFO-[tools.py:24]: executing shell output: total used free shared buff/cache available
Mem: 32064 1079 31081 3 298 30985
Swap: 8192 0 8192
Starting tool: shell_tool with inputs: {'command': 'free -m'}
Done tool: shell_tool
The memory usage is as follows:
- Total memory: 32064 MB
- Used memory: 1079 MB
- Free memory: 31081 MB
- Shared memory: 3 MB
- Buffer/cache memory: 298 MB
- Available memory: 30985 MB
The swap memory usage is as follows:
- Total swap: 8192 MB
- Used swap: 0 MB
- Free swap: 8192 MB[2025-01-18 14:04:44,322]-VIP-[agentSupervisor.py:41]: {'next': 'shell'}
[2025-01-18 14:04:44,500]-VIP-[supervisorProcess.py:97]: shell->supervisor
Starting tool: shell_tool with inputs: {'command': 'free -m'}
[2025-01-18 14:04:45,320]-INFO-[tools.py:24]: executing shell output: total used free shared buff/cache available
Mem: 32064 1079 31081 3 298 30984
Swap: 8192 0 8192
Done tool: shell_tool
[2025-01-18 14:04:45,845]-INFO-[_base_client.py:1087]: Retrying request to /chat/completions in 0.483649 seconds
The memory usage is as follows:
- Total memory: 32064 MB
- Used memory: 1079 MB
- Free memory: 31081 MB
- Shared memory: 3 MB
- Buffer/cache memory: 298 MB
- Available memory: 30984 MB
The swap memory usage is as follows:
- Total swap: 8192 MB
- Used swap: 0 MB
- Free swap: 8192 MB[2025-01-18 14:04:49,860]-VIP-[agentSupervisor.py:41]: {'next': 'shell'}
[2025-01-18 14:04:50,079]-VIP-[supervisorProcess.py:97]: shell->supervisor
[2025-01-18 14:04:50,978]-INFO-[tools.py:24]: executing shell output: total used free shared buff/cache available
Mem: 32064 1080 31080 3 298 30983
Swap: 8192 0 8192
Description
Question: check Memory Usage
TASK can't FINISH, it keeps executing the shell, I've checked response = self.llm.invoke(messages)
response is FINISH.
System Info
I add agent, run shell
class Router(TypedDict):
"""Worker to route to next. If no workers needed, route to FINISH."""
next: Literal["researcher", "coder", "shell", "FINISH"]
Question: check Memory Usage
TASK can't FINISH, it keeps executing the shell, I've checked response = self.llm.invoke(messages)
response is FINISH.
but self.llm.with_structured_output(Router).invoke(messages) response is {'next': 'shell'}, this is bug.
The text was updated successfully, but these errors were encountered:
Checked other resources
Example Code
Error Message and Stack Trace (if applicable)
Description
Question: check Memory Usage
TASK can't FINISH, it keeps executing the shell, I've checked response = self.llm.invoke(messages)
response is FINISH.
System Info
I add agent, run shell
class Router(TypedDict):
"""Worker to route to next. If no workers needed, route to FINISH."""
next: Literal["researcher", "coder", "shell", "FINISH"]
Question: check Memory Usage
TASK can't FINISH, it keeps executing the shell, I've checked response = self.llm.invoke(messages)
response is FINISH.
but self.llm.with_structured_output(Router).invoke(messages) response is {'next': 'shell'}, this is bug.
The text was updated successfully, but these errors were encountered: