Arda TANRIKULU comments

Results 597 comments of


                                            Arda TANRIKULU

Performance Issues because of AbortSignal (Execution Cancellation Plugin)

Could you test with the following alpha? `@graphql-tools/executor | 1.3.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5`

Performance Issues because of AbortSignal (Execution Cancellation Plugin)

We did a refactor there recently. Could you try it again and let us know if the performance issue persists. Also cc @enisdenjo

Performance Issues because of AbortSignal (Execution Cancellation Plugin)

Closing due to the inactivity. If the issue persisted, we can always re-open the issue! Thanks for the collaboration.

graphql query hang from browser and return error 504 Gateway Time-out after 18 minutes or so

We got some reports like hanging requests on Node 20. And we found that node-libcurl package we use was causing that. And we have removed it in Mesh v0. Could...

graphql query hang from browser and return error 504 Gateway Time-out after 18 minutes or so

We were using node-libcurl as a HTTP Client. And we got some issues reported from our users that Mesh sometimes hangs on requests to the upstream services on Node 20....

graphql query hang from browser and return error 504 Gateway Time-out after 18 minutes or so

@rxwang662001 Similar to what I said above, you can just update the versions you have in package.json, and try again.

Inferred responses are not included in the openapi spec

Responses are not inferred automatically in typescript. You have to define them explicitly.

Introspection query causes memory leaks with Remix, drizzle, pg

Thank you for creating the issue./ I guess the CodeSandbox you shared doesn't include Remix setup, so could you update it so we can reproduce the issue.

TypeError: (0 , utils_1.promiseReduce)(...).resolve is not a function

Please share a minimal isolated reproduction on CodeSandbox. Thanks!

grpc handler error: "8 RESOURCE_EXHAUSTED: Received message larger than max (6771289 vs. 4194304)"

Thanks for creating the issue! PRs are welcome if anyone is interested in implementing this missing option!