It appears that gpt-3.5-turbo 0613 doesn't specify required parameters as reliably as newer models, especially with other parameters being specified, which was breaking calls that involved filters. So this change means it will always default to the original user_query if no search_query was found in the parameters.
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
[ ] Yes
[X] No
Type of change
[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:
Purpose
It appears that gpt-3.5-turbo 0613 doesn't specify required parameters as reliably as newer models, especially with other parameters being specified, which was breaking calls that involved filters. So this change means it will always default to the original user_query if no search_query was found in the parameters.
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error? If you're not sure, try it out on an old environment.
Type of change
Code quality checklist
See CONTRIBUTING.md for more details.
:( no tests ye