fix: Reasoning.execute_tool_call() uses model.steps which does not exist in Mesa 4.x#206
fix: Reasoning.execute_tool_call() uses model.steps which does not exist in Mesa 4.x#206abhinavk0220 wants to merge 13 commits intomesa:mainfrom
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…0/mesa-llm into improve/repr-methods
…odel.steps compat
…ix/repr-and-steps-compat
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
for more information, see https://pre-commit.ci
…m/abhinavk0220/mesa-llm into fix/reasoning-mesa4x-steps-compat
|
The PR includes several unrelated changes beyond model.steps compatibility fix mentioned in the description. Please keep each PR focused on a specific change. |
Thanks for the feedback! You're right — this branch accumulated extra commits |
Summary
reasoning.pybase class hadself.agent.model.stepsin bothexecute_tool_call()andaexecute_tool_call().model.stepsdoes notexist in Mesa 4.x this caused
AttributeErroron every tool callexecution across all reasoning strategies (CoT, ReAct, ReWOO).
Fix
The same fix has already been applied in
record_model.py(PR #195)and
st_lt_memory.py(PR #199) this completes the audit acrossthe full codebase.
Testing
All existing tests pass:
AI Assistance Disclosure
This PR was developed with AI assistance (Claude) for code generation
and debugging. All code has been reviewed, tested, and understood by
the contributor.