Skip to content

fix: duplicate-GitHub penalty wipes stale_closed_pull_requests to prevent post-penalty storage (#1006) - #1131

Closed
alpurkan17 wants to merge 1 commit into
entrius:testfrom
alpurkan17:fix/1006-stale-closed-pr-penalty
Closed

fix: duplicate-GitHub penalty wipes stale_closed_pull_requests to prevent post-penalty storage (#1006)#1131
alpurkan17 wants to merge 1 commit into
entrius:testfrom
alpurkan17:fix/1006-stale-closed-pr-penalty

Conversation

@alpurkan17

Copy link
Copy Markdown
Contributor

Description

Fix #1006_zero_for_duplicate_penalty clears score-bearing PR buckets but missed stale_closed_pull_requests added in PR #769. Penalized miners' stale closed PRs survive the wipe and are still written to storage.

This bucket is storage-only (not reward-counted), so no current-round score leak. But penalized miners should be fully isolated from PR persistence after the wipe.

Changes

  • Added eval_.stale_closed_pull_requests = [] to _zero_for_duplicate_penalty

Testing

  • Duplicate miner penalized → stale_closed_pull_requests is empty → no stale PR rows written

@xiao-xiao-mao xiao-xiao-mao Bot added the bug Something isn't working label May 9, 2026
@anderdc anderdc closed this May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Duplicate-GitHub penalty leaves stale_closed_pull_requests populated, letting penalized miners continue writing stale PR rows

2 participants