Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Messenger] Keepalive support for Doctrine & Redis#20721

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
javiereguiluz merged 1 commit intosymfony:7.3fromHypeMC:update-keepalive
Mar 10, 2025

Conversation

HypeMC
Copy link
Member

@HypeMCHypeMC commentedMar 4, 2025
edited
Loading

Contains#20736 which should be merged first.

Keepalive support for the Doctrine and Redis transports was added insymfony/symfony#59601 andsymfony/symfony#59360, respectively.

Comment on lines -1748 to -1750
The keepalive feature, which prevents messages from being prematurely redelivered during
long-running processing, updates the ``delivered_at`` timestamp periodically to ensure
the message is marked as "in progress".
Copy link
MemberAuthor

@HypeMCHypeMCMar 4, 2025
edited
Loading

Choose a reason for hiding this comment

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

I don't think this is needed since no other transport has an explanation of how the keepalive mechanism is implemented and I'm not sure it's even relevant.

Copy link
Contributor

Choose a reason for hiding this comment

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

While this is an implementation detail, it could be helpful to understand the how, that said, its ok for me to remove it.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Maybe we could add a similar explanation for each transport that has the keepalive mechanism implemented?

OskarStark reacted with thumbs up emoji
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes 👍

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Done, see#20736 for 7.2

javiereguiluz added a commit that referenced this pull requestMar 10, 2025
…ansport (HypeMC)This PR was merged into the 7.2 branch.Discussion----------[Messenger] Clarify keepalive implementation for each transportAs discussed with `@OskarStark` in#20721, this PR clarifies how the keepalive mechanism is implemented for each transport.Commits-------d49a86a [Messenger] Clarify keepalive implementation for each transport
@javiereguiluz
Copy link
Member

And another nice PR! Thanks

@javiereguiluzjaviereguiluz merged commita8fc6c5 intosymfony:7.3Mar 10, 2025
2 of 3 checks passed
@HypeMCHypeMC deleted the update-keepalive branchMarch 10, 2025 10:30
OskarStark added a commit that referenced this pull requestMar 10, 2025
This PR was merged into the 7.3 branch.Discussion----------[Messenger] Fix link to class![image](https://github.com/user-attachments/assets/fad00750-a6e0-4ac5-a5dc-e522a209cf86)I broke this in#20721.Commits-------0b9fbc1 [Messenger] Fix link to class
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@OskarStarkOskarStarkOskarStark left review comments

Assignees
No one assigned
Projects
None yet
Milestone
7.3
Development

Successfully merging this pull request may close these issues.

4 participants
@HypeMC@javiereguiluz@OskarStark@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp