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.
Background
We introduced a reliance on setting openai module attributes a couple of months ago to verify model access. This was causing breakages in Azure usage not fixed by #4875 or #4098.
Known Issue: We have default fallbacks when gpt4 is not available (use gpt-3.5-turbo), but azure deployments can modify the names of models and there are no guarantees that a system will have gpt3.5 if it doesn't have gpt4. I think this is mostly a non-issue as someone using azure wants their model to fail on misconfiguration as this is most likely a user error.
Changes
Documentation
Test Plan
CI
Manual testing of
./run.sh
with no flags, with --gpt3only flag and with --gpt4only flag on an azure instance.PR Quality Checklist