Michael Lumish

I have not duplicated that problem in newer versions of Node. Can you share your test code that triggers this problem, so that we can provide more details in that...

This has been fixed in Node 20.10.0.

This question should be addressed to the firebase-admin repository. They can tell you how to use their APIs to pass options to grpc-js.

The original issue seems to have been resolved. Regarding "Stream refused by server" errors in general, since `@grpc/grpc-js` 1.8.0, this error should usually be transparently retried, so it should very...

The channel IDLE timeout has been implemented in grpc-js 1.9.x. It defaults to 30 minutes and is controlled by the `grpc.client_idle_timeout_ms` channel option.

The intention was to use the structures defined in [this gRFC](https://github.com/grpc/proposal/blob/master/L43-node-type-info.md). proto-loader implements that spec, so as far as I know, the service objects used to register services actually contain...

Yes, I would consider it valuable for us to publish a reflection library that provides the service. We would really want to have a [gRFC](https://github.com/grpc/proposal) to determine what the right...

There may be multiple causes of very similar stacktraces. Can you file a separate issue with the details of the problem you are experiencing?

That error occurs when a client receives an RST_STREAM to end the stream without receiving trailers from the server. That is a protocol error if it occurs, which is why...

How long have you been seeing this intermittently dropped data? I only published that change 4 hours ago, and it's supposed to be a fix for that problem.