Fred version - 10.1.0
Redis version - 8.0.2
Platform - Linux - Debian 12
Deployment type - centralized
Describe the bug
To Reproduce
Steps to reproduce the behavior:
- Use
RedisBuilder::build_subscriber_client similar to the pubsub example
- Start a Redis server where this is the only client
- Wait forever
Additional notes
Looking at the inner-implementations, PubsubInterface::subscribe calls fred::commands::pubsub::subscribe, which calls utils::request_response, despite the fact that the SUBSCRIBE command is documented to not return a response.
Logs
2025-06-02T20:46:49.386206Z TRACE fred::interfaces: fred-J1PsfsMGdf: Sending command SUBSCRIBE (1) to router.
The current design of our application relies on pubsubs for synchronization, and so this is deadlocking our system.
Fred version - 10.1.0
Redis version - 8.0.2
Platform - Linux - Debian 12
Deployment type - centralized
Describe the bug
To Reproduce
Steps to reproduce the behavior:
RedisBuilder::build_subscriber_clientsimilar to the pubsub exampleAdditional notes
Looking at the inner-implementations,
PubsubInterface::subscribecallsfred::commands::pubsub::subscribe, which callsutils::request_response, despite the fact that the SUBSCRIBE command is documented to not return a response.Logs
The current design of our application relies on pubsubs for synchronization, and so this is deadlocking our system.