Closed helloxz closed 1 year ago
Is there a problem with v0.5.1
Wait a minute. I'll test it first.
The same error occurs in my normal code before. It may be that ChatGPT blackened my IP or that ChatGPT upgraded the detection mechanism.
I can't use it normally. Is it still normal? Now always prompt:
{
"detail": {
"message": "Incorrect API key provided: Bearer. You can find your API key at https://beta.openai.com.",
"type": "invalid_request_error",
"param": null,
"code": "invalid_api_key"
}
}
Yes, I use the latest version and everything works fine, can you re-run
The above error still occurs. I am not sure whether it is caused by IP. I will try to change the IP tomorrow.
According to the returned information, it seems that the accesstoken has expired. You can print out the accesstoken to check whether it has expired. or
cd session
go test -run TestNewSessionWithCredential
Found the reason, it seems that my NopeCHA quota has been used up, I re-subscribed to NopeCHA, this problem no longer occurs. But a new problem arises:
{"detail":"Too many requests in 1 hour. Try again later."}
Found the reason, it seems that my NopeCHA quota has been used up, I re-subscribed to NopeCHA, this problem no longer occurs. But a new problem arises:
{"detail":"Too many requests in 1 hour. Try again later."}
The problem seems to be a limitation of openai. Even if you use chat.openai.com it will show up occasionally.
Found the reason, it seems that my NopeCHA quota has been used up, I re-subscribed to NopeCHA, this problem no longer occurs. But a new problem arises:
{"detail":"Too many requests in 1 hour. Try again later."}
The problem seems to be a limitation of openai. Even if you use chat.openai.com it will show up occasionally.
Thank you. It should be the IP. I have replaced an IP, and the situation has improved.
This hint does not need to change the ip. It will be restored after a while. I am not sure exactly what the restrictions are. You can search for keywords if you are interested.
This hint does not need to change the ip. It will be restored after a while. I am not sure exactly what the restrictions are. You can search for keywords if you are interested.
If you don't ask once, you have to wait a minute before you can ask again. It seems that this method is still unstable at present, but thank you for sharing.
I updated the version to 0.5.2, and an error occurred: