Gunter Spranz
Gunter Spranz
One more detail: The timeouts are used for the client and request object from Nodes http2 API. It is not explicitly stated in the documentation, but a passed timeout of...
I have the same problem, our grpc service is reversed-proxied behind a path /grpc (port 443). How can I access that?
Ah I think the reason is that we use grpc over HTTP/2 here so we can use REST paths. I guess grpcurl only support tcp.
This can maybe closed as duplicate of #149
Thanks for the quick reply. That is a lot of useful information. Maybe I can create a simple example server now which reproduces the error. Yes, I use `useExecutionCancellation()`, I...
Ok, I did two more tests now: First I stressed it with bombardier using a simple query like: ``` bombardier -c 3 -d 60s -l -k -H 'content-type: application/json' -m...
Ok,I got this to run on my dev machine. I will gradually expand yoga-server.ts with my setup now until I (hopefully) can reproduce the problem.
The first dependency from my service I added was fastify. So I modified yoga-server.ts from the test (see [Fastify example](https://github.com/graphql-hive/graphql-yoga/tree/main/examples/fastify): ```typescript import fastify, { FastifyReply, FastifyRequest } from 'fastify'; import...
The next dependencies I'll try to add (if Fastify doesn´t trigger the memory leak) are: - @graphql-tools/stitch - @graphql-tools/wrap - @graphql-tools/executor-http
Just found this myself, yes running now :) Results: