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
Additional context
Interesting part is if you for example subscribe to 1* and send a message on channel 1234567890123456 it seems to work again no matter the length of the channel. So it seems only * as the channel pattern is the problem.
To clarify, we dont use this in production, this is for debugging purposes only on our end.
Feel free to let me know if you need any more information on this issue, keep up the great work! Thank you
The text was updated successfully, but these errors were encountered:
…attern
If string is longer than 16 chars we are using Reflex library for
matching. When used pattern is '*' or '**' we are going to strip both of
stars and have empty pattern. We should in this edge case inject
manually star pattern.
Fixes#4948
Signed-off-by: mkaruza <mario@dragonflydb.io>
…attern
If string is longer than 16 chars we are using Reflex library for
matching. When used pattern is '*' or '**' we are going to strip both of
stars and have empty pattern. We should in this edge case inject
manually star pattern.
Fixes#4948
Signed-off-by: mkaruza <mario@dragonflydb.io>
Describe the bug
PSUBSCRIBE *
does not receive all published messages when the channel name is longer than 15 characters in length.See additional info for a special case we discovered aswell.
To Reproduce
Steps to reproduce the behavior:
PSUBSCRIBE *
PUBLISH
in a seperate redis client with a channel name longer than 15 charactersFor example
PUBLISH 1234567890123456 testvalue
Expected behavior
It should behave like redis and receive all messages published even if the channel name is longer than 15 characters.
Screenshots

Screenshot from Redis Insight Pub/Sub tool, same behavior can be reproduced using redis-cli
Environment (please complete the following information):
wsl
,k3s
on debain 12]Linux Luc-Main 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Linux *hostname redacted* 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux
Docker Compose
(Also happens in kubernetes with the operator)v1.28.1
Reproducible Docker Compose Setup
Additional context
Interesting part is if you for example subscribe to
1*
and send a message on channel1234567890123456
it seems to work again no matter the length of the channel. So it seems only*
as the channel pattern is the problem.To clarify, we dont use this in production, this is for debugging purposes only on our end.
Feel free to let me know if you need any more information on this issue, keep up the great work! Thank you
The text was updated successfully, but these errors were encountered: