diff options
| author | Taylor Mullen <[email protected]> | 2025-05-11 12:59:44 -0700 |
|---|---|---|
| committer | N. Taylor Mullen <[email protected]> | 2025-05-11 13:01:54 -0700 |
| commit | 4d5f0dc0809eacdf7c034302a5e8f36bc75ca4e1 (patch) | |
| tree | 041d8037b6817eb9fbe78d13a3f04b556a04e796 /packages/cli/src/ui/hooks/useInputHistory.ts | |
| parent | cf91f72c5c0079ec4b5db67d0f8fcac043d31088 (diff) | |
Workaround model bug where it returns invalid history items.
- 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.
Diffstat (limited to 'packages/cli/src/ui/hooks/useInputHistory.ts')
0 files changed, 0 insertions, 0 deletions