fix(gatsby): correct tracing for GraphQL queries #28415
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
vladar
removed
the
status: triage needed
KyleAMathews
approved these changes
Dec 1, 2020
pieh
pushed a commit
that referenced
this pull request
Dec 4, 2020
(cherry picked from commit 4e50d5c)
pieh
pushed a commit
that referenced
this pull request
Dec 4, 2020
(cherry picked from commit 4e50d5c)
pieh
pushed a commit
that referenced
this pull request
Dec 4, 2020
(cherry picked from commit 4e50d5c) Co-authored-by: Vladimir Razuvaev <[email protected]>
|
Published in |
pragmaticpat
pushed a commit
to pragmaticpat/gatsby
that referenced
this pull request
Apr 28, 2022
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
Before this PR
GraphQL Querytrace was reporting incorrect numbers. It was always reporting0-5msbecause we didn't wait for the query promise to resolve. So the tracer was ending immediately after theexecute()call.