Update wall of shame reasons#727
Merged
Merged
Conversation
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.
Groups Wall of Shame data by validator/operator and shows a single Shame column with per-network reasons, while hiding unknown rows from the UI. Persists metrics, logs, and node-version shame start dates, adds outdated-version grace-period handling, and extends endpoint tests around grouped reasons and persisted shame duration. Makes featured-content seeding idempotent, adds migration dependencies for validator waitlist points, and ensures the project participants through table exists. Adds the validator shame timestamp migration and updates the workspace package-lock name.