Sharing same @EventPattern across 2 handlers is broken if 2nd handler uses an interceptor

Bug Report

Current behavior

Given two controller route handlers that subscribe to the same @EventPattern, both handlers are executed as expected. However, if an interceptor is used on the 2nd handler, the interceptor is executed but the handler itself is never executed

Input Code

Reproduce: https://github.com/RoxKilly/nestjs-redis-troubleshoot/tree/issue-7913

export class AppController implements OnModuleInit {
  constructor(@Inject('REDIS_CLIENT') private redis: ClientRedis) {}

  onModuleInit(): any {
    this.redis.emit(eventPattern, 'NEW EVENT');
  }

  @EventPattern(eventPattern)
  handler1(data) {
    Logger.log(data, 'Handler 1');
  }

  /** This will not be triggered unless we disable the interceptor or remove the other handler */
  @EventPattern(eventPattern)
  @UseInterceptors(LoggingInterceptor)
  handler2(data) {
    Logger.log(data, 'Handler 2');
  }
}

Without Interceptor

Notice that both handler1 and handler2 receive and log the NEW EVENT

With Interceptor on 2nd handler

Notice the interceptor for handler2 is triggered, but handler2 never executes (it doesn’t log the event)

Expected behavior

I expected both handlers to be triggered even if I use an interceptor on the 2nd handler.

Possible Solution

Removing the interceptor from the 2nd handler makes this go away but is not a practical workaround.

Environment

Nest version: 8.0.6

 
For Tooling issues:
- Node version: 16.4.0 
- Platform:  Windows

Others:

[kamilmysliwiec]

Fixed in 8.0.9

[davidgabrichidze]

@HackPoint never, so far. I mean, ... Event pattern: undefined never showed to me. When there is no listener, message always shows name of pattern.