Skip to content
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

Nested asynchronous resolvers in a subscription #960

Closed
art1415926535 opened this issue May 4, 2019 · 2 comments
Closed

Nested asynchronous resolvers in a subscription #960

art1415926535 opened this issue May 4, 2019 · 2 comments

Comments

@art1415926535
Copy link

My subscription class have nested objects. The first level asynchronous resolver working perfectly. The second level breaks subscription request and not produce any response.

Ok:
{ async { sync } }

Breaks:
{ async { async } }

I created a test project with examples above:
https://github.com/art1415926535/async_subscription_error/blob/master/test.py

@ekampf ekampf added the 🐛 bug label May 6, 2019
@stale
Copy link

stale bot commented Jul 29, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 29, 2019
@art1415926535
Copy link
Author

The problem is solved.

graphql-python/graphql-ws#12 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants