You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Messages should be posted into the stream-name stream, and consumed using worker-group group. However, messages are posted into messages stream, and consumed using symfony group name - you can check this on redis-cli: XPENDING messages worker-group yields "NOGROUP No such key 'messages' or consumer group 'worker-group'".
Using querystring parameters to configure the same options works just fine.
The text was updated successfully, but these errors were encountered:
This PR was merged into the 4.3 branch.
Discussion
----------
[Messenger] Fix ignored options in redis transport
| Q | A
| ------------- | ---
| Branch? | 4.3
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#33425
| License | MIT
| Doc PR | -
Also fixes redis authentication failure handling (inline with invalid db index handling, borrowed from symfony/cache).
/cc @alexander-schranz
Commits
-------
c83ff94 [Messenger] Fix ignored options in redis transport
Symfony version(s) affected: 4.3.4
Description
According to the documentation, Redis should be configurable using the
options
object, but this seems not to work.How to reproduce
Messages should be posted into the
stream-name
stream, and consumed usingworker-group
group. However, messages are posted intomessages
stream, and consumed usingsymfony
group name - you can check this on redis-cli:XPENDING messages worker-group
yields"NOGROUP No such key 'messages' or consumer group 'worker-group'"
.Using querystring parameters to configure the same options works just fine.
The text was updated successfully, but these errors were encountered: