Improve the error logging for OAI Issues #1987
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BillSchumacher
approved these changes
Apr 17, 2023
sindlinger
pushed a commit
to Orgsindlinger/Auto-GPT-WebUI
that referenced
this pull request
Sep 25, 2024
…ror-msgs Improve the error logging for OAI Issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This is a QoL update for a user facing issue that seems to be pretty common: users not setting up paid accounts and inevitably getting hit with a nasty exception vaguely telling them: "Failed to get response after x retries". This doesn't help anyone.
This PR just improves the logging for this common issue by outputting better logs and directing the user to possible causes for hitting the rate limit.
Changes
Added better logging in
llm_utils.pyin thecreate_chat_completionfunction.PR Quality Checklist