Made #active_questions post more robust against hicups #476
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
Zabuzard
force-pushed
the
feature/make_active_questions_robust
branch
from
e9c80f6 to
ecbe112
Compare
|
Kudos, SonarCloud Quality Gate passed! |
marko-radosavljevic
approved these changes
Aug 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Overview
We have an ongoing issue with the question overview in
#active_questionsbeing posted twice (a moderator is then usually pinged and deletes the duplicate). This happens roughly once or twice a week.The cause of this are likely Discord hicups where the codes history-lookup can not locate the message, even though it is actually there.
This mitigates the issue, while still preserving the intended feature of having a fresh message post if the message is truly not the recent message in the channel, by allowing it to fail up to 3 times before it decides to send a fresh message.