Michael Lumish
Michael Lumish
It's definitely not supposed to do that, for unary or streaming RPCs. And the [`session.close()` documentation](https://nodejs.org/api/http2.html#http2sessionclosecallback) explicitly says that it doesn't do that, so this sounds like a bug in...
On my machine, your example works with earlier versions of Node. It looks like they broke something in Node 16.7.
I have filed nodejs/node#42713
This should already work. This was previously reported in #1717, and I made the fix for the plugin in #1725, and then that change was published in version 1.11.1.
OK, there are a couple of issues here. Tracking down the source of these errors may be tricky for the reasons you mentioned, but they are definitely the result of...
Well, grpc doesn't throw that error. It just passes it along to the client (Datastore, in this case). I am fairly certain that Datastore propagates the error as a promise...
These logs show that the HTTP/2 streams are being closed with RST_STREAM frames with error codes 2 (INTERNAL_ERROR) and 11 (ENHANCE_YOUR_CALM which translates to RESOURCE_EXHAUSTED). It is very likely (but...
Thank you for sharing those extra details.
I made a change in grpc-js version 1.2.0 that changed the timing of keepalive pings. That may address some of the problems reported here.
PR #1666 has been published in grpc-js version 1.3.0. It adds a channel option `grpc-node.max_session_memory`. Setting that to a value larger than 10 may stop these RESOURCE_EXHAUSTED errors from happening...