go-resiliency icon indicating copy to clipboard operation
go-resiliency copied to clipboard

Resiliency patterns for golang

Results 4 go-resiliency issues
Sort by recently updated
recently updated
newest added

Imagine that I have an application that is an event processor that connects to some event log and for every event that arrives I want to do something with it....

Users of the `retrier` package may wish to configure a retrier with a global timeout that applies across all retries. This differs from the `backoffs` configuration because each individual backoff...

If the retrier encounters a context-related error, such as `context.DeadlineExceeded` while attempting retries of `work()`, the context error is returned. This means the actual error from `work()` never bubbles up....

The standard library has a https://pkg.go.dev/context#example-WithDeadline. Does that implement the same functionality as deadline? If so, should deadline be deprecated in the next major version of this library?