Skip to content

draft: fix: Don't release lock for ShouldBeUniqueUntilProcessing Job that gets released #54261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Jan 22, 2025

Conversation

mathiasgrimm
Copy link
Contributor

@mathiasgrimm mathiasgrimm commented Jan 19, 2025

When a job that is ShouldBeUniqueUntilProcessing is released, it releases the UniqueLock causing multiple Jobs to be present in the queue when it should be only a single one

mathiasgrimm and others added 5 commits January 19, 2025 15:55
…ts released

Verified

This commit was signed with the committer’s verified signature.
StyleCIBot StyleCI Bot
…rocessing' into fix-job-should-be-unique-until-processing
…ts released
@mathiasgrimm mathiasgrimm changed the title draft: fix: Don't release lock for ShouldBeUniqueUntilProcessing Job that get released draft: fix: Don't release lock for ShouldBeUniqueUntilProcessing Job that gets released Jan 19, 2025
mathiasgrimm and others added 7 commits January 19, 2025 16:05
…ts released
…ts released
…ts released

Verified

This commit was signed with the committer’s verified signature.
StyleCIBot StyleCI Bot
…rocessing' into fix-job-should-be-unique-until-processing

Verified

This commit was signed with the committer’s verified signature.
StyleCIBot StyleCI Bot
@taylorotwell taylorotwell merged commit c2c35e9 into 11.x Jan 22, 2025
39 checks passed
@taylorotwell taylorotwell deleted the fix-job-should-be-unique-until-processing branch January 22, 2025 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants