-
Notifications
You must be signed in to change notification settings - Fork 12
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
the server responded with status 400 (Faraday::BadRequestError) with Gemini API key #21
Comments
I'm happy to troubleshoot and file a PR myself, I just need help on how to enable Faraday logging (to see what API call is being made and what JSON is being returned). |
This is the faraday dump. Seems like NO response body is available, just a "mute" 400.
|
Hi @palladius! Thank you very much for reporting the issue. I identified the root cause and I'm working on a fix in this PR: |
@palladius fixed in version 3.2.0: gem 'nano-bots', '~> 3.2' Update: Actually, prefer the newer version 3.4.0: gem 'nano-bots', '~> 3.4' |
You are a STAR! I took a look at #22 . Nice job! |
Hi, I'm trying to use nanobots with Gemini API key and keep failing repeatedly. after some debugging, I can see that
gemini-ai
andcurl
work great with my API key, while nb fails to work.For convenience the code is all here: https://github.com/palladius/ragazzi
I thought I might have a bad key, but then I tried this with same key and that worked:
==>
Please help
The text was updated successfully, but these errors were encountered: