Fix test_tool_choice_none_after_tool_results test failure #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The
test_tool_choice_none_after_tool_resultstest added in PR #50 fails with:This was reported by @paxiaatucsdedu in #50 (comment)
Root Cause
The test used non-existent OCI SDK classes and had several issues:
models.Toolwhich doesn't exist in the OCI SDKtool_choice=noneafter any ToolMessage, but the actual implementation only sets it when:max_sequential_tool_callslimit is exceeded, ORstopparameter in_prepare_request()callSolution
Fixed the test to:
max_sequential_tool_calls=3limitstopparameter to_prepare_request()callChanges
libs/oci/tests/unit_tests/chat_models/test_oci_generative_ai.pymodels.Toolwith Python functionget_weather(city: str)_prepare_request()call signatureTest Results
Before: ❌ FAILED
After: ✅ PASSED
All 6 tool-related unit tests now pass:
Impact
Related: