Repository navigation
feat(server): configure an explicit request body limit - #430
Merged
Merged
Conversation
mayborn005
force-pushed
the
fix/issue-353
branch
from
October 27, 2026 12:56
91293bf to
534cab7
Compare
Contributor
|
Hi @Ashborne267 — I rebased PR #430 onto the current base and resolved the conflicts; GitHub now reports it mergeable. The safety check passes. The fresh Lint, typecheck, test workflow still fails on the current base in unrelated files, including unused declarations in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BODY_LIMIT_BYTES.413 { "error": "payload_too_large" }response.This is a dedicated assignee-authored PR for #353. The broader open PR #391 also references this issue.
Validation:
git diff --checkpassed. Local Vitest could not run because dependencies are not installed (vitest: command not found).Closes #353.