You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Describe the bug
When a query times out, if there's a following query right away it will not even go to the resolver and just return the value of the previously timed out query, even if they are two completely different queries with different schemas.
To Reproduce
Steps to reproduce the behavior:
Make you resolver take longer than the configured time out, if you are using the default it will be 30s
Issue a query to the server
Right after the query times out issue another query
Your first query will get the Execution canceled because timeout of 30000 millis was reached response
Your second query will have the response payload from the first timed out query
Expected behavior
Both queries should have the Execution canceled because timeout of 30000 millis was reached response
UPDATE: it only happens when graphql.servlet.async.enabled is true
The text was updated successfully, but these errors were encountered:
Describe the bug
When a query times out, if there's a following query right away it will not even go to the resolver and just return the value of the previously timed out query, even if they are two completely different queries with different schemas.
To Reproduce
Steps to reproduce the behavior:
Execution canceled because timeout of 30000 millis was reached
responseExpected behavior
Both queries should have the
Execution canceled because timeout of 30000 millis was reached
responseUPDATE: it only happens when graphql.servlet.async.enabled is true
The text was updated successfully, but these errors were encountered: