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.

Sign up for GitHub

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

Jump to bottom

Handlers could be executed twice after a Message release #91

Closed
masterjus opened this issue Mar 18, 2022 · 0 comments · Fixed by #92
Closed

Handlers could be executed twice after a Message release #91

masterjus opened this issue Mar 18, 2022 · 0 comments · Fixed by #92
Assignees
@masterjus
Labels
bug
Milestone
v7.0

Comments

@masterjus
Copy link
Contributor

Description:
Let's imagine hat we have 3 listeners on an event.

The first Listener was successfuly ran. The second was failed and the Message has been released. The third Listener was skept because the second failed.

The Message is back to the queue and we try to process it again. First Listener will be executed again.

Expected Result: Successful Listeners should not be executed after a Message release.
@masterjus masterjus added this to the v7.0 milestone Mar 18, 2022
@masterjus masterjus added the bug label Mar 18, 2022
@masterjus masterjus self-assigned this Mar 18, 2022
masterjus pushed a commit that referenced this issue Mar 22, 2022
@eugene-nuwber
#91 Run handler once
fba4427
@masterjus masterjus linked a pull request Mar 22, 2022 that will close this issue
#91 Run handler once #92
Merged
@masterjus masterjus mentioned this issue Mar 22, 2022
Merged
masterjus added a commit that referenced this issue Mar 22, 2022
@masterjus @eugene-nuwber
#91 Run handler once (#92)
b50c577 
Co-authored-by: Eugene Kirdzei <e.ki@nuwber.com>
masterjus pushed a commit that referenced this issue Mar 22, 2022
@eugene-nuwber
Issue #91 Run job once
503bbab
masterjus added a commit that referenced this issue Mar 22, 2022
@masterjus @eugene-nuwber
Issue #91 Run job once (#93)
d949fef 
Co-authored-by: Eugene Kirdzei <e.ki@nuwber.com>
@masterjus masterjus reopened this Oct 5, 2022
masterjus pushed a commit that referenced this issue Oct 5, 2022
@eugene-nuwber
#91: Real fix for only one event exchange
2f174b1
@masterjus masterjus mentioned this issue Oct 7, 2022
Merged
masterjus added a commit that referenced this issue Oct 7, 2022
@masterjus @eugene-nuwber
#91: Real fix for only one event exchange (#100)
65cfa79 
* #91: Real fix for only one event exchange

* Set correct routing key

* Fix tests

* Config

Co-authored-by: Eugene Kirdzei <e.ki@nuwber.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@masterjus masterjus

Labels
bug
Projects
Nuwber's RabbitEvents
Status: Done
Milestone
v7.0
Development

Successfully merging a pull request may close this issue.

#91 Run handler once nuwber/rabbitevents
1 participant
@masterjus