Properly fix website pin migration#1066
Merged
Toastbrot236 merged 3 commits intoLittleBigRefresh:mainfrom Apr 4, 2026
Merged
Conversation
Contributor
Author
|
Tested this once more, it works |
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.
Found another pagination issue with this migration right after merging the previous PR, so I've (partially) reworked it to iterate users instead of pin relations.
This does make the newly introduced feature to alter the processed and total counts in the
JobStateunused for now, but I have not removed it because it might eventually become necessary, if a different job ever needs to delete entities.