fix(scrape): raise default max_body_bytes from 1 MiB to 4 MiB#1130
Merged
fix(scrape): raise default max_body_bytes from 1 MiB to 4 MiB#1130
Conversation
Pages like documentation sites commonly exceed 1 MiB of raw HTML. The previous limit caused spurious "response too large" errors on legitimate scrape requests. 4 MiB covers most real-world pages while still preventing unbounded memory usage. Updated insta snapshot and all affected unit tests.
github-actions
bot
added
rust
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.
Summary
default_max_body_bytesfrom 1 048 576 (1 MiB) to 4 194 304 (4 MiB) inScrapeConfigconfig_default_snapshot) and all affected unit test assertionsTest plan
cargo nextest run --workspace --lib --bins— all 3374 tests passcargo clippy --workspace -- -D warnings— zero warningscargo +nightly fmt --check— clean