debian-forge-composer/vendor/github.com/cenkalti/backoff/v4
Ondřej Budai 0359647a82 go.mod: update to Go 1.18
Fedora 35 support was dropped, so we can update to a newer Go.

Stable RHEL 8 and 9 and Fedora 36 ships Go 1.18, so let's switch to it.

"//go:build" directives are now apparently enforced by go fmt, so that's why
there were added.

Also, all the github actions were adjusted to use Go 1.18.

Signed-off-by: Ondřej Budai <ondrej@budai.cz>
2023-01-09 14:03:18 +01:00
..
.gitignore go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
.travis.yml go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
backoff.go auth: OpenID/OAUth2 middleware 2021-09-04 02:48:52 +02:00
context.go go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
exponential.go go.mod: Update openshift-online/ocm-sdk-go 2022-05-19 22:18:42 +02:00
LICENSE auth: OpenID/OAUth2 middleware 2021-09-04 02:48:52 +02:00
README.md go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
retry.go go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
ticker.go go: update most dependencies to the latest version 2021-09-05 12:50:02 +01:00
timer.go auth: OpenID/OAUth2 middleware 2021-09-04 02:48:52 +02:00
tries.go auth: OpenID/OAUth2 middleware 2021-09-04 02:48:52 +02:00

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.