Jay Povey

> Sometimes connections get dropped for reasons outside of the library's control. Just retry the call when that happens. The client will reconnect when you do. > > In addition,...

Thanks for the info and the link. Just an FYI to the rest of thee thread, downgrading node to `16.8.0` did not resolve the `ECONNRESET [{"message":"14 UNAVAILABLE: read ECONNRESET"}]` issue...

I am using node `16.8.0` and i have downgrade too ``` "@grpc/grpc-js": "1.2.1", "@grpc/proto-loader": "0.5.1", ``` and now the `ECONNRESET [{"message":"14 UNAVAILABLE: read ECONNRESET"}]` has seemed to have disappear for...

Ah damn, yes i am, it has just happend sporadically again. do you think it could be an issue with NestJs (the framework i use). It uses grpc-js under the...

That makes sense, thanks i'll give it a try. Thanks for all the help, appreciate it, been pulling my hair out.

Hey, so i have been poking around a lot today and whilst i do not have an answer i have some findings. I use docker-compose to bring up all the...

I am unsure, the instantiation of the `grpc-js` client happens under the hood in the `nest-js` framework. ill dig into the code and take a look. on another note, i...