4d5f0dc080
- Currently there's a bug in the API (or SDK?) where the SDK endpoint will commonly fail with:
```
Error: Failed to generate JSON content: got status: 400 Bad Request. {"error":{"code":400,"message":"* GenerateContentRequest.contents[5].parts: contents.parts must not be empty.\n","status":"INVALID_ARGUMENT"}}
```
- At times the model will respond with an empty parts list where if we send that back up to the API endpoint it explodes with the above. Using a curated history seems like a total hack around this prolbem, and even in the SDK (i'm following up on this), BUT helps mitigate this issue.
|
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
| index.ts | ||
| package.json | ||
| tsconfig.json | ||
README.md
Nested package template. Either fill this out with "backend" functionality or create similar packages that you want built separate from the CLI.
To use this package from another dependent package in this monorepo:
- add
"@gemini-code/server"to the dependent package'spackage.json - import in a dependenant by calling
import { } from "@gemini-code/server"