Improve awaitable errors #285
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
wravery
force-pushed
the
improve-awaitable-errors
branch
from
838491d
to
19101d0
Compare
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.
I tried running the
clientHTTP sample without starting theserver, and I noticed that theBoost.Beasterror from failing to connect was not being handled gracefully.In the process of adding error reporting to the
client, I realized that exceptions thrown from awaitable resolvers are caught in theObject::resolvemethod instead of theSelectionVisitor::visitFieldmethod, and they are missing the field location and path information. We only report the error message.