[fadiroot]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

With wildcards: true, ServerRedis listens for pmessage, which ioredis emits as (pattern, channel, message). The handler is registered on the pattern (e.g. users.*) and is looked up correctly, but the reply for a request-response message is also published to users.*.reply.

Redis does not expand globs on PUBLISH, and ClientRedis subscribes to the reply channel of the concrete channel it published to (users.created.reply), so the reply never reaches the client and every client.send() against a wildcard handler hangs until it times out. Events are unaffected because they do not reply.

Repro:

// server
@MessagePattern('users.*')
handle() { return 'ok'; }

// client
await lastValueFrom(client.send('users.created', {})); // never resolves

What is the new behavior?

The reply is published to the channel the request came from (users.created.reply), which is what ServerMqtt already does for its wildcard topics. Without wildcards the channel and the pattern are the same value, so nothing changes there.

A unit test covers the wildcard case in server-redis.spec.ts.

Does this PR introduce a breaking change?

• Yes
• No

Other information