Michael Lumish

@n0v1 The main problem is the types. I suggest looking at #2230, and the comments in particular, for a previous attempt at this. In short, the type of the `options`...

As mentioned in the linked Deno issue, the current implementation of HTTP/2 in Deno is inadequate for implementing gRPC, and that is a fundamental obstacle to porting `@grpc/grpc-js` in particular...

I think the conspicuous absence of anything called `http2` anywhere in the Deno standard library implies that `denoify` would not handle this library effectively.

Unfortunately, according to denoland/deno#10214, trailing headers will not be supported in Deno's HTTP/2 implementation. Trailers are critical to the gRPC protocol, so without them it is not compatible.

Sure. Once those changes are actually released, we can start investigating this concretely.

It looks like the Deno `std` package provides both [`setImmediate`](https://deno.land/[email protected]/node/timers.ts?s=setImmediate) and [`process.nextTick`](https://deno.land/[email protected]/node/process.ts?s=nextTick).

OK, `setImmediate` is not a big loss, because it should be functionally equivalent to `setTimeout(fn, 0)`. Losing `process.nextTick` is more unfortunate because it schedules the operation sooner, before polling on...

To clarify, does the ALB drop the connection after 60 seconds of inactivity, or just 60 seconds after it is created? If it is inactivity, is the client inactive for...

The GOAWAY is not the problem here. A GOAWAY with code 0 indicates "no error", i.e. that the client should stop creating new streams on the connection, but existing streams...

@mehulparmariitr This issue cannot be "solved" entirely because not every instance of this error is the fault of this library. And it looks like you are not even getting this...