Repository navigation
List at most 10 duplicate slots per locale in Discord - #70
Merged
Merged
Conversation
A locale past 10 new or resolved slots lists the first 9, then the count left and a link to the locale in the Crowdin editor, rather than splitting into "(cont.)" embeds. A one-locale burst like Korean's 462 slots is one message instead of 14, which ran into Discord's per-channel rate limit and failed the run.
mpretty-cyro
approved these changes
Oct 6, 2026
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.
On 2026-10-06 crowdin-duplicates found 462 new duplicate slots in Korean and split them over 14 Discord messages. Discord rate-limited message 13, so the run failed without writing its state.
Each locale is now one embed: up to 10 slots with editor links, or the first 9 and
…and N more: open <locale> in the editorlinking to the locale in the Crowdin editor. That applies to new and resolved slots alike. The state still records every slot.Bursts across many locales still post several messages back to back. Pacing posts in
post_to_discordis the fix for that, and is not in this PR.Testing
python -m unittest discover -s tests -t .: 778 OK; ruff clean.