Michael Lumish

The `grpc-js` library does not directly emit the `end` event or handle that error you are throwing, so I think that behavior is coming from the Node stream implementation. I...

I see what you're saying now. I think there's a reasonably easy fix for this.

On further examination, I don't actually know how to fix this. The relevant code is kind of convoluted.

If I `npm install grpc-tools`, I see the `LICENSE` and `README.md` files in `node_modules/grpc-tools` and they both contain the expected content. The `grpc-tools` page on the npm website contains the...

The original issue said that the LICENSE and README.md files are not present in the tarball. They are in fact present, which is why I closed the issue. The problem...

Since `@grpc/grpc-js` version 1.8.0, servers support the options `grpc.max_connection_age_ms` and `grpc.max_connection_age_grace_ms` to close connections after they have been open for a certain period of time. This does not only apply...

As of `@grpc/grpc-js` version 1.10.2, servers can now drop idle connections. That behavior is configured with the `grpc.max_connection_idle_ms` options.

I can change this, but depending on what exactly you're trying to accomplish here, you may get a better effect from a different server API.

OK, I think you would find the new `unbind` API useful. You can unbind the specific port that you want to make unavailable, and then bind it again later.

The difference in output from `checkOptionalUnaryResponseArguments` is probably not related to the problem. It looks like the same object is returned in both cases, but Bun is printing the contents...