Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Messenger] Resend failed retries back to failure transport #51848

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 1 commit into from
Oct 5, 2023
Merged

[Messenger] Resend failed retries back to failure transport #51848

merged 1 commit into from
Oct 5, 2023

Conversation

ro0NL
Copy link
Contributor

@ro0NL ro0NL commented Oct 4, 2023

Q A
Branch? 6.4 / 5.4
Bug fix? yes
New feature? yes
Deprecations? no
Tickets Fix #51815
License MIT

i want to argue this is a bugfix :)

i can confirm with this fix, you can indefinitely retry failures, till they succeed, are deleted manually, or are handled explicitly by other means. What should NOT happen is systems implicitly rejecting/acking messages without any confirmation whatsoever.

cc @fabpot, @weaverryan

@carsonbot
Copy link

Hey!

Thanks for your PR. You are targeting branch "6.4" but it seems your PR description refers to branch "6.4 / 5.4".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

@weaverryan
Copy link
Member

That code goes all the way back to the original PR for the failure transport system. I can't remember why I had this, however. Since we're dealing with the failure transport, this seems like a safe area, but I'd still probably do it for 6.4.

@fabpot
Copy link
Member

fabpot commented Oct 5, 2023

Thank you @ro0NL.

@fabpot fabpot merged commit 34a93ef into symfony:6.4 Oct 5, 2023
@ro0NL ro0NL deleted the patch-1 branch October 5, 2023 07:08
This was referenced Oct 21, 2023
fabpot added a commit that referenced this pull request Feb 25, 2024
…transport " (ro0NL)

This PR was merged into the 6.4 branch.

Discussion
----------

[Messenger] Revert "Resend failed retries back to failure transport "

Reverts #51848

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead -->
| License       | MIT

See #53216, it's complex :')

I suggest to get rid of confusion between `messenger:consume failed` vs. `bin/console messenger:failed:retry` somehow.

cc `@beermeat` `@guelosuperstart` `@javaDeveloperKid` `@fabpot`

Commits
-------

8dba632 [Messenger] Revert "Resend failed retries back to failure transport "
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Messenger] Requeue failed retries
4 participants