Skip to content

[Messenger] allow DeduplicateStamp to be serialized #60677

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

Closed
wants to merge 1 commit into from

Conversation

kbond
Copy link
Member

@kbond kbond commented Jun 3, 2025

Q A
Branch? 7.3
Bug fix? yes
New feature? no
Deprecations? no
Issues Possible solution for #60667
License MIT

I'm not 100% sure this is the proper solution as Key state would be lost during serialization. I don't know enough about the Lock component to know if this is a problem in this case.

@stof
Copy link
Member

stof commented Jun 4, 2025

This is totally wrong. Big -1 from me.
Serializing the Key is precisely what allows the messenger consumer to release a lock that was acquired when dispatching the message to the bus. Your change breaks the feature entirely.

This middleware (and stamp) is documented to be compatible only with lock storages that support key serializations to transfer keys to another PHP process. Not all stores support this feature: https://symfony.com/doc/current/components/lock.html#available-stores

@kbond
Copy link
Member Author

kbond commented Jun 4, 2025

Got it, closing.

@kbond kbond closed this Jun 4, 2025
@kbond kbond deleted the deduplicate-stamp-serialize branch June 4, 2025 11:09
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.

3 participants