Test demonstrating a query planner bug (probably) #2680
Closed
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
|
✅ Deploy Preview for apollo-federation-docs canceled.
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
This test passes. However, the "bad" query plan shows something blatantly messed up: a Sequence(Fetch, Flatten) where the Flatten uses a path (graph.variant.graph.accountForPersistedQueriesSubgraph) not mentioned in the Fetch.
glasser
force-pushed
the
glasser/bad-subgraph-query-plan
branch
from
a8d5d5a
to
cf17230
Compare
trevor-scheer
added a commit
that referenced
this pull request
Jul 19, 2023
This commit reapplies #2639 with an additional fix related to reproducing and resolving #2680. The bug existed in the SelectionSet.contains logic in the final check to provide a ContainsResult. Here the lengths of the compared selection sets are used to determine subset or strictly equal. In the case that the __typename field was ignored up above, the comparison becomes invalid unless we offset the comparison by 1 to account for the non-existent field.
trevor-scheer
added a commit
that referenced
this pull request
Jul 19, 2023
This commit reapplies #2639 with an additional fix related to reproducing and resolving #2680. The bug existed in the SelectionSet.contains logic in the final check to provide a ContainsResult. Here the lengths of the compared selection sets are used to determine subset or strictly equal. In the case that the __typename field was ignored up above, the comparison becomes invalid unless we offset the comparison by 1 to account for the non-existent field.
trevor-scheer
added a commit
that referenced
this pull request
Jul 19, 2023
This commit reapplies #2639 with an additional fix related to reproducing and resolving #2680. The bug existed in the SelectionSet.contains logic in the final check to provide a ContainsResult. Here the lengths of the compared selection sets are used to determine subset or strictly equal. In the case that the __typename field was ignored up above, the comparison becomes invalid unless we offset the comparison by 1 to account for the non-existent field.
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.
This test passes. However, the "bad" query plan shows something blatantly messed up: a Sequence(Fetch, Flatten) where the Flatten uses a path (graph.variant.graph.accountForPersistedQueriesSubgraph) not mentioned in the Fetch.