-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openai.error.APIConnectionError #3
Comments
Hi @lemon1-ui Have you set your API_KEY in the user_params.py file after runing |
The problem with Chart 3 should be related to connecting to OpenAI API. Please retry and let me know if you still face the same issue. The problem with Closure should be related to extracting bug information for Closure bugs. I guess some setting is not set or library is not installed, and that's the problem. We will need to update the README to ensure all the requirements are installed for extracting bug info. As a temporary solution, you can unzip the |
@khaes-kth Hi,sorry to bother you again.I would like to ask how to decompress cache/cache. tar. gz. a * files? |
No worries @lemon1-ui You should be able to decompress the files following the instructions here. Particularly, I guess you can cd to |
@khaes-kth The problem with Closure has been solved.But I still failed to connect to OpenAI API.How can I solved it? |
@lemon1-ui Can you double check what model you are using in your prog_params.py file? It seems the |
@khaes-kth I just tried to change gpt-3.5-turbo-0301 to gpt-3.5-turbo, but the same error still occurred. |
@khaes-kth Hi,I'm so sorry to bother you again.I tried to change gpt-3.5-turbo-0301 to other versions, Chart 1 could be repairred successfully, when I tried to fix other bugs, the error as followed.How can I solved it? Thanks so much! |
Hi @lemon1-ui We can set up a remote meeting if you want to check this out. It is hard to guess what is going on just by looking at these logs. |
Hi,Dr.Dávid,when I ran the ./cigar.sh Chart 1, the errors as follow: how can I resolve it?
The text was updated successfully, but these errors were encountered: