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
Some query errors are only thrown on execution or preparation in sangria which causes the following code to fail in F instead of in Either[Throwable, Json] even though the error is in fact a graphql error.
Field 'field' conflict because they return conflicting types 'A!' and 'A'. Use different aliases on the fields to fetch both if this was intentional. (line n, column k):
field
(line x, column y):
field
When this occurs the subscription "hangs", no error or anything, which seems to be because a fiber is started but does not interact with the subscription in case of any error outcomes.
ValdemarGr
changed the title
Unfortunate handling og query validation in subscriptions in sangria.
Unfortunate handling of query validation in subscriptions in sangria.
Apr 21, 2022
Some query errors are only thrown on execution or preparation in sangria which causes the following code to fail in
F
instead of inEither[Throwable, Json]
even though the error is in fact a graphql error.lucuma-graphql-routes/modules/sangria/src/main/scala/lucuma/graphql/routes/SangriaGraphQLService.scala
Lines 63 to 83 in 2051089
An example of this is the following error:
When this occurs the subscription "hangs", no error or anything, which seems to be because a fiber is started but does not interact with the subscription in case of any error outcomes.
lucuma-graphql-routes/modules/core/src/main/scala/lucuma/graphql/routes/Subscriptions.scala
Line 93 in 2051089
We have deployed the following fix:
The text was updated successfully, but these errors were encountered: