Report and enforce effective managed-data upload limits - #92
Merged
Merged
Conversation
obsessixnv
added
bug
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
1 participant
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.
A complete data file could be rejected by the 1 MiB managed-data envelope limit after MCP advertised 1.5 MB inline support or recommended an unlimited staged upload. The server now distinguishes compact payload, escaped envelope, inline transport, staged file and complete HTTP request limits using resolved startup configuration.
Domain overflow reports measured bytes, the applicable limit and whether changing transport can help. Optional advisory
data_sizemeasurements reject known-impossible uploads before reserving a handle; actual content is independently validated on consume. Existing clients and whitespace-heavy JSON remain supported, with no sampling, truncation, capacity increase or migration. Data upload responses and tool/prepared-prompt guidance expose the effective limits.Validation on the combined branch after #91: 269 unit tests, 293 browser tests, and full throwaway-Postgres integration, including exact boundaries, escaping/UTF-8, runtime overrides, real HTTP request boundaries/direct PUT separation, omitted/understated measurements, and unchanged versions/audit/upload state on failure. Production dependency audit and shell syntax pass. Independent review found no blocking issues. CI covers the supported Node matrix and browser workflows.
Closes #39.