Ignore RecordNotUnique errors in LinkCrawlWorker #28748
Merged
Conversation
This file contains 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
ClearlyClaire
approved these changes
Jan 16, 2024
ClearlyClaire
pushed a commit
that referenced
this pull request
Jan 17, 2024
ClearlyClaire
pushed a commit
that referenced
this pull request
Jan 23, 2024
This was referenced Jan 23, 2024
ClearlyClaire
pushed a commit
that referenced
this pull request
Jan 24, 2024
ClearlyClaire
pushed a commit
that referenced
this pull request
Jan 24, 2024
noellabo
pushed a commit
to fedibird/mastodon
that referenced
this pull request
Jan 24, 2024
kmycode
pushed a commit
to kmycode/mastodon
that referenced
this pull request
Jan 24, 2024
ttrace
pushed a commit
to ttrace/mastodon
that referenced
this pull request
Feb 2, 2024
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.
Somehow(I think it is race condition), LinkCrawlWorker raises
RecordNotUniqueerror. But it is safe to ignore and don't leave trace on sidekiq dashboard