-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
fix(gatsby): workaround graphql-compose issue #29822
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gatsbot
bot
added
the
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
label
Feb 27, 2021
vladar
added
topic: GraphQL
Related to Gatsby's GraphQL layer
and removed
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
labels
Feb 27, 2021
sidharthachatterjee
approved these changes
Feb 27, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! Thank you @vladar
I have a plan for how to fix this problem in graphql-compose but it will take months. Sorry, suppose this workaround may stay with you for months 😉 I found vladar's workaround very elegant and don't see any problems. |
vladar
added a commit
that referenced
this pull request
Feb 28, 2021
* fix(gatsby): workaround graphql-compose issue * freeze after building (cherry picked from commit 7f9bcf1)
vladar
added a commit
that referenced
this pull request
Feb 28, 2021
* fix(gatsby): workaround graphql-compose issue * freeze after building (cherry picked from commit 7f9bcf1) Co-authored-by: Vladimir Razuvaev <[email protected]>
This was referenced Mar 9, 2021
This was referenced Mar 9, 2021
This was referenced Mar 9, 2021
This was referenced Apr 15, 2024
This was referenced May 16, 2024
This was referenced Oct 13, 2024
This was referenced Oct 15, 2024
This was referenced Oct 15, 2024
This was referenced Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We've noticed that the query running step on v3 is pretty slow. After investigation, the issue was discovered in
graphql-compose
: graphql-compose/graphql-compose#319This PR is a workaround for it. But the proper fix should be added in
graphql-compose
itself. Once fixed upstream, we can remove this workaround.