-
Notifications
You must be signed in to change notification settings - Fork 184
crash when connecting gql to hasura #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: bug
An issue or pull request relating to a bug
Comments
Hi, Could you please post here the complete error message ? The PR #94 should fix your issue |
Thanks! The relevant part of the stack trace was this:
And this was the hasura reply {'errors': [{'extensions': {'path': '$', 'code': 'validation-failed'}, 'message': 'no such operation found in the document: ""'}]} |
leszekhanusz
added a commit
that referenced
this issue
Jun 14, 2020
Fix connecting to servers which do not support setting operationName to "" (#92)
Fixed in version v3.0.0a1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm trying this client with hasura and it crashes when executing the introspection query due to
https://github.com/graphql-python/gql/blob/master/gql/transport/aiohttp.py#L109
If that line is just
operation_name
instead ofoperation_name or ""
then it works. Hasura breaks when the operationName is set to""
.Not positive if this is a hasura issue or a gql issue.
The text was updated successfully, but these errors were encountered: