How can I see gRPC server streaming sessions?

[ncsibra]

Hi,

Where can I see the active gRPC server streaming connections?
They're working fine, I get the messages in the output view when choosing "httpyac - GRPC", but otherwise can't find them anywhere.
Not shown in the "Session" view and it's not even in the "History", only after closing the connection.
Checked with httpbook too, but didn't see any info about those.

It's should be shown somewhere, most likely in "Session" or the "active session" view in httpbook.
Currently I don't know how to terminate them (currently closing VSCode) and don't know how many of them are still active without getting a message.

[AnWeber]

Hi I agree with you. The behavior is still not quite ideal. For individual clients I already use the session store for storage and reuse (e.g. AMQP), but not for all. I think it's best to implement this generically.
Currently, however, a popup should actually be open that shows the running process abortable. Is this not working correctly?

[AnWeber]

@ncsibra I need help with that. I can't readjust/check it and to me the behavior looks right. I am now correctly calling client.close (docs). The connectivitystate before the close is 2 = Ready, after close 4 = shutdown. And that actually all looks correct and I do not know what more I need to do.. Could you provide me a server and the necessary steps how to reproduce the error?
I'll make one more attempt now without an example. There is a cancel method on the stream. Maybe I have to call this instead of the destroy I expect.

[ncsibra]

I will try to create a small sample server, but the cancel method sounds promising, so worth a try.

[ncsibra]

@AnWeber Here's a sample server: https://github.com/ncsibra/grpc-examples/tree/main/route_guide
It's written in Go, if you need a binary instead, let me know the platform, and I will create one.
I added a very simple sample .http file too.
After calling ListFeatures it will send a message every 100s, 100 messages in total, logging after every sending and will log when it finished or the client cancelled the call.

After some testing pretty sure that calling cancel will be the solution.
When testing in Postman I can see the cancelled log in the server, but when removing the session in httpyac it just logs the sendings until finished.

[AnWeber]

I have now set it up in a dev container. Thanks for the example. And yes calling the cancel method seems to solve the problem. Without it the server rattles through all 100 entries. Now when I use my dev branch it stops after cancel.

2023/10/23 19:12:22 22. feature sent
2023/10/23 19:12:23 23. feature sent
2023/10/23 19:12:23 context canceled during sleep
2023/10/23 19:12:23 ListFeatures finished

Apparently it is not enough for grpc to terminate the stream using destroy/ end, but you have to explicitly use the API. But cool found I hope. I will release the state and then you can still test it please. And big thanks for your example. It was super helpful.

[ncsibra]

Looks like it's working correctly, thanks for the fix!