Skip to content

Issues: parzh/retryable

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.

Sign up for GitHub

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

5 Open 21 Closed
5 Open 21 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider interop between retry.__ suite and possible retryable(fn, params) signature Domain: meta [Issue / PR] describes change in the development process, documentation, maintenance etc. Priority: high [Issue / PR] must be addressed as soon as possible Type: investigation [Issue / PR] addresses the need of gaining intel
#97 opened Jun 21, 2021 by parzhitsky
Create API for retrying throwed functions and rejected promises Change: minor [Issue / PR] describes a non-breaking change, such as adding a new functionality Domain: main [Issue / PR] describes change in the functionality, its optimization Pending: blocked [Issue / PR] cannot be addressed until another issue is resolved Pending: unclear [Issue] not yet fully defined Priority: medium [Issue / PR] should be addressed without delay Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement
#96 opened Jun 19, 2021 by parzhitsky
5
Use ms package to allow human-readable delays Change: minor [Issue / PR] describes a non-breaking change, such as adding a new functionality Domain: main [Issue / PR] describes change in the functionality, its optimization good first issue [Issue] can be addressed by a first-time contributor Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement
#92 opened Jun 1, 2021 by parzhitsky
Write comprehensive docs Change: patch [Issue / PR] describes a small non-breaking change, such as bugfix or an optimization Domain: main [Issue / PR] describes change in the functionality, its optimization good first issue [Issue] can be addressed by a first-time contributor Pending: unclear [Issue] not yet fully defined Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement
#52 opened Feb 7, 2020 by parzhitsky
Remove deprecated entities Change: major [Issue / PR] describes a breaking change of any kind Domain: main [Issue / PR] describes change in the functionality, its optimization Pending: unclear [Issue] not yet fully defined Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement
#12 opened Jan 31, 2020 by parzhitsky
3 tasks
ProTip! Find all open issues with in progress development work with linked:pr.