mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-11-19 22:43:38 +00:00
* 🧱 fix: Bound Attachment Reads and Keep Bedrock's Document Limit
`getFileStream` buffered a stored object in full for every provider and every
kind of attachment, and the Bedrock document limit was `configured ??
provider`. The merged file config always carries a size limit (512 MB by
default), so with any `fileConfig` section Bedrock's 4.5 MB limit never
applied: an 8 MiB CSV was downloaded, decoded and serialized before Bedrock
refused it.
The shared reader takes a byte limit and stops at the first chunk past it. A
Bedrock document is refused from its recorded size before storage is opened,
read under that limit so an object larger than its record cannot reach memory
either, and reported as a 413 attachment error. A configured limit can lower
Bedrock's limit and no longer raise it.
* fix: Let a Set Limit Override Bedrock's, Keep Replay Tolerant
A limit the operator set overrides Bedrock's own, up or down, as it does for
other providers. What no longer counts is the 512 MB the merge fills in for
every endpoint, which is how the provider limit was lost whenever a
`fileConfig` section existed.
Replayed history skips the recorded-size refusal so an object that is gone is
still reported missing and left out; the bounded read refuses one that is
present. The client shows the size refusal under its attachment-limit
headline, not as a provider failure.
|
||
|---|---|---|
| .. | ||
| openapi | ||
| src | ||
| types | ||
| .gitignore | ||
| babel.config.cjs | ||
| jest.config.mjs | ||
| jest.setup.cjs | ||
| package.json | ||
| tsconfig.build.json | ||
| tsconfig.json | ||
| tsconfig.openapi.json | ||
| tsconfig.spec.json | ||
| tsdown.config.mjs | ||