-
Notifications
You must be signed in to change notification settings - Fork 2k
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 trace placement for errors occurring in lists #7699
Conversation
✅ Deploy Preview for apollo-server-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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. Latest deployment of this branch, based on commit d661279:
|
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.
I think you probably also want to reach out to Pulsar internally to ensure that our usage report ingestion code will properly notice and handle errors on list nodes in traces. (Feel free to ping me on that request to stay in the loop.)
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.
lgtm modulo the concern about GraphOS ingestion
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @apollo/server-integration-testsuite@4.9.2 ### Patch Changes - Updated dependencies \[[`62e7d940d`](62e7d94)]: - @apollo/server@4.9.2 ## @apollo/server@4.9.2 ### Patch Changes - [#7699](#7699) [`62e7d940d`](62e7d94) Thanks [@trevor-scheer](https://github.com/trevor-scheer)! - Fix error path attachment for list items Previously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message: > `Could not find node with path x.y.1, defaulting to put errors on root node.` This change places these errors at their correct paths and removes the log. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Fixes #4476
Currently, when errors occur while resolving a list item, the trace builder fails to place the error at the correct path and just defaults to the root node with a warning message:
This change places these errors at their correct paths and removes the log.