Skip to content
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

[10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should process only once #49294

Closed
wants to merge 3 commits into from

Conversation

tntsoft
Copy link

@tntsoft tntsoft commented Dec 9, 2023

This test was created in order to replicate #49263

Testing if a unique job that is chained multiple times only triggers once.

Testing if a unique job that is chained multiple times only triggers once
@tntsoft tntsoft changed the title [10.x] [DRAFT] Bus chianed unique jobs fired multiple times should trigger only once. [10.x] [DRAFT] Bus chained unique jobs fired multiple times should trigger only once. Dec 9, 2023
@tntsoft tntsoft changed the title [10.x] [DRAFT] Bus chained unique jobs fired multiple times should trigger only once. [10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should trigger only once. Dec 9, 2023
@tntsoft tntsoft changed the title [10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should trigger only once. [10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should process only once. Dec 9, 2023
@tntsoft tntsoft changed the title [10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should process only once. [10.x] [DRAFT] Bus chained unique jobs dispatched multiple times should process only once Dec 9, 2023
@GrahamCampbell GrahamCampbell marked this pull request as draft December 9, 2023 15:20
Copy link
Member

@GrahamCampbell GrahamCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"exactly once" is impossible to achieve. The only two choices are at most once or at least once. The usual trade-off is at least once.

@driesvints
Copy link
Member

Closing this PR because it's inactive, already solved, old or not relevant anymore. Feel to open up a new PR if you're still experiencing this.

@driesvints driesvints closed this Mar 5, 2024
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.

4 participants