-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add Error Handling for Canceled Contexts during request lifecycle #1277
Comments
This is already the case -- consumers must always inspect the received context, and return if it is finished. |
That's fair, but would it make sense to treat the Server as a consumer of the context and "bail" if the context is finished early? |
@peterbourgon I'm curious if there's been any updates here? I'm running into this issue myself and wondering if we could bake cancellation Thank you! |
What would you like?
Various lifecycle steps can cancel a
context.Context
, but it would be the responsibility of each consumer to verify the context isn't canceled. It would be great to add:The text was updated successfully, but these errors were encountered: