-
Notifications
You must be signed in to change notification settings - Fork 2
Define retry.setMaxCount #76
Copy link
Copy link
Closed
Labels
Change: minor[Issue / PR] describes a non-breaking change, such as adding a new functionality[Issue / PR] describes a non-breaking change, such as adding a new functionalityDomain: main[Issue / PR] describes change in the functionality, its optimization[Issue / PR] describes change in the functionality, its optimizationPriority: low[Issue / PR] could be addressed at any convenient time[Issue / PR] could be addressed at any convenient timeType: improvement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement[Issue / PR] addresses lack of a functionality or an open possibility of enhancementgood first issue[Issue] can be addressed by a first-time contributor[Issue] can be addressed by a first-time contributor
Metadata
Metadata
Assignees
Labels
Change: minor[Issue / PR] describes a non-breaking change, such as adding a new functionality[Issue / PR] describes a non-breaking change, such as adding a new functionalityDomain: main[Issue / PR] describes change in the functionality, its optimization[Issue / PR] describes change in the functionality, its optimizationPriority: low[Issue / PR] could be addressed at any convenient time[Issue / PR] could be addressed at any convenient timeType: improvement[Issue / PR] addresses lack of a functionality or an open possibility of enhancement[Issue / PR] addresses lack of a functionality or an open possibility of enhancementgood first issue[Issue] can be addressed by a first-time contributor[Issue] can be addressed by a first-time contributor
Definition:
Usage:
(All actions here are limited to 3 attempts total: one initial attempt and two additional retries.)
Idempotence
Setting maximum retry count is an idempotent action, — only the first call (per each
retryentity) will take effect. This also includes subsequent calls of the same line when retrying the attempt.One big example with multiple
retryentities: