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

Work constantly stops with "contents.parts must not be empty" #1585

Open
iandouglas opened this issue Mar 9, 2025 · 1 comment
Open

Work constantly stops with "contents.parts must not be empty" #1585

iandouglas opened this issue Mar 9, 2025 · 1 comment
Assignees

Comments

@iandouglas
Copy link

Describe the bug

I'm providing a detailed prompt to Goose to help build an app and set up some infrastructure, but Goose barely gets started before appearing to stop working. When I ask Goose to continue, I get an error that looks like this:

Ran into this error: Request failed: Request failed with status: 400 Bad Request. Message: * GenerateContentRequest.contents[7].parts: contents.parts must not be empty. .

To Reproduce
Steps to reproduce the behavior:

  1. Use Gemini Flash 2.0 or Flash 2.0 Exp
  2. Give it a bunch of instructions all at once
  3. See error

Expected behavior
It's odd that work would just "stop" and Goose returns to a prompt like it's waiting for something to do, and then to return this error.

Screenshots

Image

Please provide following information:

  • OS & Arch: This happens on Ubuntu Linux 22.04 using Goose CLI, and on MacOS using the Goose GUI
  • Interface: both, UI on Mac, and CLI o Linux
  • Version: v1.0.12
  • Extensions enabled: None to my knowledge
  • Provider & Model: Google Gemini, I've tried 2.0 Flash and 2.0 Flash-Exp

Additional context
The prompt file I'm providing to Goose lists instructions like "help me build a Python/FastAPI project with Alembic database migrations" where I give it a detailed list of parameters, and for the database I give it the database credentials and table names to make etc. but then it just ... stops working.

@yingjiehe-xyz
Copy link
Collaborator

@iandouglas can you share the session and log? you can find the log under ~/.local/state/goose/logs/cli/xxx/xxxxx-xxxx.log

@yingjiehe-xyz yingjiehe-xyz self-assigned this Mar 11, 2025
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