Skip to content
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

generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT response starting between 9AM and 2PM Pacific on 2024-11-11 #627

Closed
jxyzn opened this issue Nov 11, 2024 · 2 comments

Comments

@jxyzn
Copy link

jxyzn commented Nov 11, 2024

Description of the bug:

Running this same script with a previously function API key results in
{ "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT" } }

I have records of proper results from my code using the API before ~9:02 AM today. My next attempt at using this same API occurred at 1:54PM and returned this error. In attempting to figure out what happened, I resorted to trying this sample script which I'd based my processing on. It is now returning this same error.

Actual vs expected behavior:

A proper response from the test query.

Any other information you'd like to share?

This API key is still functional; other (text-only, no upload) prompt give appropriate results.

@jxyzn jxyzn changed the title generative-ai-python/samples/rest /files.sh no longer functions starting between 9AM and 2PM Pacific on 2024-11-11 generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT starting between 9AM and 2PM Pacific on 2024-11-11 Nov 11, 2024
@jxyzn jxyzn changed the title generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT starting between 9AM and 2PM Pacific on 2024-11-11 generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT response starting between 9AM and 2PM Pacific on 2024-11-11 Nov 11, 2024
@adboio
Copy link

adboio commented Nov 12, 2024

+1 seeing this issue - commented on #628 with details

@jxyzn
Copy link
Author

jxyzn commented Nov 12, 2024

This was the same issue as 628, which has been closed. Closing this.

@jxyzn jxyzn closed this as completed Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants