For example:
When setting up a retry policy like so:
azure.storage.common.ExponentialRetry(
initial_backoff=3,
increment_power=2,
max_attempts=3)
This sounds like it will result in a retry sequence of: {3, 3 + 1^2, 3 + 2^2} (since increment_power is 2, the powers/exponents are all 2). In reality it generates a sequence {3, 3 + 2^1, 3 + 2^2}
Luckily, this is all clarified by the documentation here:
|
Constructs an Exponential retry object. The initial_backoff is used for |
Still, it would be more clear if this were called increment_base rather than increment_power since the "power"/exponent is actually n (number of retries) and is not configurable by the user.
For example:
When setting up a retry policy like so:
This sounds like it will result in a retry sequence of:
{3, 3 + 1^2, 3 + 2^2}(sinceincrement_poweris 2, the powers/exponents are all 2). In reality it generates a sequence{3, 3 + 2^1, 3 + 2^2}Luckily, this is all clarified by the documentation here:
azure-storage-python/azure-storage-common/azure/storage/common/retry.py
Line 158 in 9b5e870
Still, it would be more clear if this were called
increment_baserather thanincrement_powersince the "power"/exponent is actuallyn(number of retries) and is not configurable by the user.