Bring "egregious range request" comment in line with reality
With MAX_RANGES pulled out as a constant, developers are likely to just trust the comment rather than go verify the value. Change-Id: I47fbd4790492b272d53ee07fe5bc87170ce2c72b Releated-Change: I4dcedcaae6c3deada06a0223479e611094d57234
This commit is contained in:
parent
7a166cccfb
commit
f35829c291
@ -586,7 +586,7 @@ class Range(object):
|
||||
#
|
||||
# We're defining "egregious" here as:
|
||||
#
|
||||
# * more than 100 requested ranges OR
|
||||
# * more than 50 requested ranges OR
|
||||
# * more than 2 overlapping ranges OR
|
||||
# * more than 8 non-ascending-order ranges
|
||||
if len(all_ranges) > MAX_RANGES:
|
||||
|
Loading…
Reference in New Issue
Block a user