ticker: document it's unsafe to access backoff policy while ticker running #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nning The other way around would be to use locks to make backoff policies thread-safe. This is not something hard to do but this would need to be implemented in each policy. It doesn't seem unreasonable to require the user to not modify the backoff policy while we are using it. Fix cenkalti#47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The other way around would be to use locks to make backoff policies
thread-safe. This is not something hard to do but this would need to
be implemented in each policy. It doesn't seem unreasonable to require
the user to not modify the backoff policy while we are using it.
This would fix #47 (for some definition of "fix").