Open gabizou opened 12 months ago
it would be the responsibility of each consumer to verify the context isn't canceled
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 if ctx.Err() == context.Canceled
into the request lifecycle.
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: