Bug: NATS-based RPC call responding to an initial pub/sub message results in spurious empty message about faststream

[Lancetnik]

FastStream sends your handler result for all rpc or reply_to requests as a response automatically
If you want to process these cases manually and prevent such behavior, you should use no-reply subscriber @broker.subscriber(..., no_reply=True)

[Lancetnik]

I think, we can close it

[maxalbert]

Thanks for the reply and clarification @Lancetnik. Indeed, this solves the issue and confirms that things are working as intended on the FastStream side.