unary_stream message issue

I'm currently facing the issue that a unary_stream connection does not behave as I would expect. (betterproto version b5)

## Client code:

## Server code:

Opening the connection works fine, the server receives the request and begins its job.
The task the server performs is taking 1 min +/-, during that time it sends multiple responses to the client.
While debugging I could see that subroutines have been executed and sending data (server side).

But nothing arrives at the client, the red X located at the client if statement is a breakpoint that never executes until after the server method returns. If I breakpoint the server at its last statement (red X) the client is idle. Only after continuing, allowing the server to complete the method (closing the connection?), within the client program the subroutines trigger:

All messages then are 'spammed' to the waiting client. At first glance, nothing is missing, but I expected the stream to work like in the default google implementation. Receiving the messages one after another when sent from the server.
Is this intended behavior?

Reproduce el ejemplo unary_stream de cliente y servidor mostrado en el issue con betterproto b5 y observa cuándo recibe mensajes el cliente mientras el servidor sigue ejecutándose. Compara ese comportamiento con la semántica de streaming esperada y determina si la entrega antes de que retorne el método del servidor es intencionada; se considera terminado cuando el comportamiento esté explicado y estén claros el cambio apropiado en el proyecto o el alcance de las pruebas.

Escrito por el modelo de indexación a partir del texto del issue.