mirror of https://github.com/hashicorp/boundary
internal/event: avoid reusing canceled context (#5304)
Don't error in ReleaseGate if the context used for the original event has been cancelled. Any error in ReleaseGate causes the controller to terminate its startup. If a user was trying to send a request to the Boundary controller as it started up, the context tied to the request would be reused to attempt logging the observation associated with the request after the logging gate was released. This would always fail, as the context associated with the request was canceled. We now use a new context timeout for events logged after the release gate is released, if the original context was canceled.pull/5305/head
parent
22a9074724
commit
c85fad27f6
Loading…
Reference in new issue