-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add retries to contribution #1483
Comments
@mandar-brave do we have spec for this flows? I know that we wanted to do it, but not sure if we ever did |
Hey @nejc Zdovc <nejc@brave.com> - see the link at the bottom of David's BR
spec - it links to an excel. This was discussed separately as a state
system and is in its own tab.
Alternatively, i can add all failure/transitional state changes in the spec.
R, Mandar
…On Wed, Oct 10, 2018 at 3:35 AM Nejc Zdovc ***@***.***> wrote:
@mandar-brave <https://github.com/mandar-brave> do we have spec for this
flows?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1483 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AiRIkzgl6zzXIBtbJZMuvK8ZFQm4zeTZks5ujc15gaJpZM4XVDPk>
.
--
Best, Mandar
|
@NejcZdovc we have an existing spec. @mrose17 please assign to yourself if necessary. |
@NejcZdovc moving priority to P1 based on feedback and some community issues re: Tipping. |
Thanks @mandar-brave 👍 |
blocked on #1987 |
Verified passed with
Verification passed on:
Verification passed on Brave 0.57.8 Chromium: 71.0.3578.53 (Official Build) beta (64-bit)
|
We need to handle all error paths and do retries when necessary.
We will have two refactors prior to that
The text was updated successfully, but these errors were encountered: