Repository navigation
feat/aggregate-report-flagging-limitations - #1090
Merged
Merged
Conversation
…s evidence in disputes based on dispute category
danflo27
approved these changes
Oct 30, 2026
danflo27
added
noStateChange
backport release/v6.x
and removed
noStateChange
backport release/v6.x
labels
danflo27
added
noStateChange
backport release/v6.x
and removed
noStateChange
backport release/v6.x
labels
CJPotter10
added a commit
that referenced
this pull request
Oct 30, 2026
* added limits for how many aggregate reports can be flagged and used as evidence in disputes based on dispute category * fixed test to not tip a cyclelist query (cherry picked from commit d4ff750) Co-authored-by: CJPotter10 <91627020+CJPotter10@users.noreply.github.com>
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.
Description
made it so that no micro reports that are also the aggregate report for that query can be used as evidence in a warning dispute and up to only 1 aggregate report can be submitted as evidence in a minor dispute. A user can still open a dispute on any micro report regardless of the dispute category or if it is an aggregate report (if you dispute an aggregate report as a minor dispute that counts as your 1 aggregate report flagged).
This should protect against someone being able to flag a bunch of aggregate reports for a lower cost
Related Issue
Fixes #
Type of Change
Testing
added some e2e and integration tests to verify new logic and tweaked unit tests to match new logic
Checklist