Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to configure fixed or back off delay #12

Merged
merged 1 commit into from
Jan 11, 2019
Merged

Conversation

sjanota
Copy link
Contributor

@sjanota sjanota commented Jan 11, 2019

This PR adds additional Option: DelayType. It allows to switch between different delay calculation algorithms. There are two for now: FixedDelay which takes the same delay value every iteration, and BackOffDelay which works as previously. BackOffDelay is default.

@codecov-io
Copy link

codecov-io commented Jan 11, 2019

Codecov Report

Merging #12 into master will increase coverage by 0.49%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage      96%   96.49%   +0.49%     
==========================================
  Files           2        2              
  Lines          50       57       +7     
==========================================
+ Hits           48       55       +7     
  Misses          2        2
Impacted Files Coverage Δ
options.go 100% <100%> (ø) ⬆️
retry.go 94.73% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7e26136...4b5b36d. Read the comment docs.

@JaSei JaSei merged commit 48dfe71 into avast:master Jan 11, 2019
@JaSei
Copy link
Collaborator

JaSei commented Jan 11, 2019

Thanks for you PR...

@codyaray
Copy link

awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants