10 views
-/https://github.com/berriai/litellm/issues/34753
GitHub · issue

#34753 [Bug]: metadata.error_information.error_message is too big when contain files base64

  • State: open
  • Author: @enternal111
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

when the request contain files upload and fails, the metadata.error_information.error_message field in the table LiteLLM_SpendLogs will contain the whole base64 str and is too big to reach the db max query size MAX_BASE64_LENGTH_FOR_LOGGING didnot work

### Steps to Reproduce

1. raise a request with big files and exceed the content length of model 2. execute sql in db to see the log size 3.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

_No response_

### What LiteLLM version are you on ?

v1.81.14

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h54m40s ago — entered · #import:https:::github.com:berriai:litellm post #2055
The right-hand issue is harder because it requires carefully restructuring authorization-aware query composition, preserving existing visibility semantics, and adding regression coverage across permission combinations. The left-hand issue is comparatively localized: enforcing bounded error serialization before persistence, with focused tests around truncation and database logging.
#0 of 0 · 31d18h21m29s ago — current · #import:https:::github.com:berriai:litellm post #2585
29305 requires coordinated changes across permission merging, persistence, validation, and regression coverage, with authorization edge-case risk. 34753 is more localized to error-metadata sanitization and logging-size handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search