-
Notifications
You must be signed in to change notification settings - Fork 69
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
Batching requests is not supported anymore #72
Comments
Hey there! I think this was due to this API switching from Apollo Server to GraphQL Yoga a little while ago. And it seems like batching is disabled by default in Yoga: https://the-guild.dev/graphql/yoga-server/docs/features/request-batching So I made a commit that enables it: 398df27 Hope that helps :) |
Hey, Thanks! |
Ah, I see what's going on. I recently introduced a rate limit to deal with some users abusing the API by sending 100s of uncachable, erroneous requests per second, and blowing up my Cloudflare workers free usage limit as a result. Unfortunately, batch queries is currently incompatible with Stellate's rate limiting feature: https://stellate.co/docs/graphql-rate-limiting/alpha-limitations#graph-ql-query-batching I really want to support this feature, but I also know that unless I have another plan in place to deal with spamming requests, disabling rate limiting will cause the entire API to be unresponsive once per day, if it continues to get hammered by invalid requests. Perhaps there's yet another (hopefully free) service I can put infront of Stellate to deal with the rate limiting issue. Would appreciate any ideas or recommendations, if you have any! |
I understand. |
No worries! I'll keep thinking about this and hopefully come up with a good solution soon. I'll post back here with any updates. Thanks for bringing this to my attention! |
It was working in September when we developed the functionality for the gql Python client.
Could it be possible to bring that functionality back?
In the meantime, I'm disabling those tests on our side.
The text was updated successfully, but these errors were encountered: