Sebastiaan van Stijn 35b238ee82
vendor: vendor with -compat=1.17
This might break compatibility with projects using this module that
are still on go1.16, which is EOL, so probably ok to ignore:

    github.com/docker/buildx/store imports
        github.com/gofrs/flock tested by
        github.com/gofrs/flock.test imports
        gopkg.in/check.v1 loaded from gopkg.in/check.v1@v1.0.0-20200227125254-8fa46927fb4f,
        but go 1.16 would select v1.0.0-20201130134442-10cb98267c6c

    To upgrade to the versions selected by go 1.16:
        go mod tidy -go=1.16 && go mod tidy -go=1.17
    If reproducibility with go 1.16 is not needed:
        go mod tidy -compat=1.17
    For other options, see:
        https://golang.org/doc/modules/pruning

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
..
.gitignore vendor: update buildkit to opentelemetry support
.travis.yml vendor: update buildkit to opentelemetry support
LICENSE vendor: update buildkit to opentelemetry support
README.md vendor: update buildkit to opentelemetry support
backoff.go vendor: update buildkit to opentelemetry support
context.go vendor: update buildkit to opentelemetry support
exponential.go vendor: update buildkit to opentelemetry support
retry.go vendor: update buildkit to opentelemetry support
ticker.go vendor: update buildkit to opentelemetry support
timer.go vendor: update buildkit to opentelemetry support
tries.go vendor: update buildkit to opentelemetry support

README.md

Exponential Backoff GoDoc Build Status Coverage Status

This is a Go port of the exponential backoff algorithm from Google's HTTP Client Library for Java.

Exponential backoff is an algorithm that uses feedback to multiplicatively decrease the rate of some process, in order to gradually find an acceptable rate. The retries exponentially increase and stop increasing when a certain threshold is met.

Usage

Import path is github.com/cenkalti/backoff/v4. Please note the version part at the end.

Use https://pkg.go.dev/github.com/cenkalti/backoff/v4 to view the documentation.

Contributing

  • I would like to keep this library as small as possible.
  • Please don't send a PR without opening an issue and discussing it first.
  • If proposed change is not a common use case, I will probably not accept it.