goose
goose copied to clipboard
Cryptic suggestion in CLI, missing reference in troubleshooting for rate limit exceeded for Google Gemini
Describe the bug
Note: Please check some common questions on https://block.github.io/goose/docs/troubleshooting before filing the report [Done]
A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Open a goose version 1.0.12 or 1.0.12-canary+2383de5 CLI session (same results with both).
- Provide any simple prompt, ex. "How do I show the git short SHA1 hash for a code repository?".
- See error
( O)> How do I show the git short SHA1 hash for a code repository?
◓ Building response chains... 2025-03-07T18:35:13.102875Z ERROR goose::agents::truncate: Error: Request failed: Request failed with status: 400 Bad Request. Message: * GenerateContentRequest.contents[13].parts: contents.parts must not be empty.
at crates/goose/src/agents/truncate.rs:399
Ran into this error: Request failed: Request failed with status: 400 Bad Request. Message: * GenerateContentRequest.contents[13].parts: contents.parts must not be empty.
.
Please retry if you think this is a transient or recoverable error.
- Exec
rm -rf ~/.config/gooseper troubleshooting. - No change in observed behavior.
Expected behavior
Initially, return a response similar to: git rev-parse --short HEAD. After diagnosing the issue, return a less cryptic suggestion than Please retry if you think this is a transient or recoverable error..
Please provide following information:
- OS & Arch: [Ubuntu 24.04.01 x86]
- Interface: [CLI]
- Version: [1.0.12 and 1.0.12-canary+2383de5]
- Extensions enabled: [Computer Controller, Developer, Memory]
- Provider & Model: [Google - gemini-2.0-flash]
Additional context This was a rate limit issue. The HTTP status code 400 does not match any troubleshooting doc.