Detect rapid submission replays - #225
Merged
Merged
Conversation
pierres
force-pushed
the
detect-rapid-submission-replays
branch
from
September 3, 2026 09:28
05e9f18 to
b1b4382
Compare
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.
Adds rapid exact-replay detection to
detect-anomalies.\n\nA replay is the same IP, payload hash, and user agent repeated within the two-hour deduplication window. The command reports all detections and exits with the existing high-confidence status when they exceed 0.1% of the month's logged reports.\n\nTested withjust testand against the copied production database: July reports 604 replays (2.059% of logged reports); September reports none.