Bound server memory usage when reviewing large untracked files#1118
Open
kcosr wants to merge 1 commit into
Open
Bound server memory usage when reviewing large untracked files#1118kcosr wants to merge 1 commit into
kcosr wants to merge 1 commit into
Conversation
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.
When an unignored build artifact or binary file appears in Git status, Plannotator can consume several gigabytes of server-side memory even if the rendered diff is small.
This PR keeps those files visible without loading their contents into memory. It also:
/api/file-contentLarge untracked files over 5 MiB are displayed as binary additions. Smaller files continue to behave normally, including manual hunk expansion.
Validated with focused tests, full TypeScript checks, and production builds for the review UI and hook.
Related to #940.