Repository navigation
Conversation
…_read organization_max_bytes_to_read and organization_referrer_max_bytes_to_read both mean "cap this org's queries". Replace them with one max_bytes_to_read setting, set per org or referrer in a match block. Neither is set today.
Member
Author
|
Combined into #8642. |
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.
BytesScannedRejectingPolicy has two param settings that both mean "cap this org's queries at N bytes and skip the scan window":
organization_max_bytes_to_readandorganization_referrer_max_bytes_to_read.This replaces both with one
max_bytes_to_readsetting. Per-org or per-referrer values go in match blocks.-1is unset.