Maurits
Results
1
comments of
Maurits
@huan With an application I'm working on I'm seeing the same GRPC error. It uses `grpc` as well: can you confirm whether this behavior magically disappeared after migrating to `@grpc/grpc-js`?