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

Skip to content

[Messenger] reset connection on worker shutdown #45910

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

Conversation

SanderHagen
Copy link
Contributor

Q A
Branch? 4.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #45778
License MIT

As seen in the issue. Amazon SQS transport uses a buffer. Messages can be lost when the buffer contains these messages and some container executing the process is shut down. The connection contains a reset method and implements the ResetInterface. If this method were to be called on shutdown the messages will be marked as visible again.

@carsonbot
Copy link

Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

  • Always add tests
  • Keep backward compatibility (see https://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
  • Features and deprecations must be submitted against the 6.1 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

@@ -101,7 +101,7 @@ public function run(array $options = []): void
}
}

$this->dispatchEvent(new WorkerStoppedEvent($this));
$this->dispatchEvent(new WorkerStoppedEvent($this, $this->receivers));
Copy link
Member

Choose a reason for hiding this comment

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

I'd prefer not adding a new class + argument

instead, we could add the reset loop after this call, isn't it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

True, good idea 👍

@fabpot fabpot force-pushed the ticket_45778_reset_receiver_connections_on_worker_stop branch from 998c0eb to c486305 Compare April 1, 2022 14:34
@fabpot
Copy link
Member

fabpot commented Apr 1, 2022

Thank you @SanderHagen.

@fabpot fabpot merged commit a4c8f4e into symfony:4.4 Apr 1, 2022
@fabpot fabpot mentioned this pull request Apr 2, 2022
This was referenced Apr 27, 2022
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.

4 participants