Skip to content
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

Retries for unverified Publishers #3741

Closed
hollons opened this issue Mar 15, 2019 · 4 comments · Fixed by brave/brave-core#2512
Closed

Retries for unverified Publishers #3741

hollons opened this issue Mar 15, 2019 · 4 comments · Fixed by brave/brave-core#2512

Comments

@hollons
Copy link

hollons commented Mar 15, 2019

Description

Current spec

  • keep each a/c and tips separate; convert all a/c values to tips once creator-XX is verified
  • when a new publisher is verified, notify once that a publisher is verified "We will send your contributions to newly verified creator-XX" - action OK and close
  • Try sending every tip based on time sequence, FIFO
  • if tips fail, keep them in pending log at the browser till successful
  • if tips fail due to lack of funds, notify first time ONLY when users retry that "You have pending tips due to insufficient funds" - action " Add funds" and drives to add-funds and close
  • (Re) try every day

Each of the notifications ONLY the first time; one time for every verified publisher and one time only for failed retries due to lack of funds.

Obsolete spec
Part-2 of the unverified spec
https://docs.google.com/document/d/1y9eTyvvRkRXIDnRuCJ7SDzhK53kUnjsmuK9ZsGxnDiM/edit?usp=sharing

@NejcZdovc NejcZdovc added the priority/P1 A very extremely bad problem. We might push a hotfix for it. label May 1, 2019
@mandar-brave
Copy link

mandar-brave commented May 1, 2019

prioritizing the issue for immediate nightly builds
@NejcZdovc @davidtemkin @evq @jenn-rhim @alexwykoff

Issue:
Currently all unverified Publisher contributions are stuck on the browser edge. However, if any of those publishers sign up, the retries for such held contributions is not retried.

What needs to happen: Tips and A-C

  • A-C unverified will be considered as tips
  • Against an unverified publisher, create one large TIP summing up all pending transactions

Step-1

  • Try sending the transaction if budget permits as a single tip
    Step-2
  • If that does not work, use the budget to pay the tip to max
  • if any tip is sent, the first time create a notification for the user "Your tip of "XX" BAT to unverified "creator YY" was sent (only for amount sent)
  • Keep a table for pending tips
  • Check every day if there is budget and repeat step-1
    Step-3
    If multiple publishers qualify on any day, the one with the earliest timestamp trumps

@NejcZdovc NejcZdovc self-assigned this May 1, 2019
@NejcZdovc
Copy link
Contributor

@mandar-brave some adjustments:

Against an unverified publisher, create one large TIP summing up all pending transactions
We will not merge them together as in almost all cases user will not have enough funds.

I wrote the whole thing how this could work, but at the end I got a lot of edge cases. I think we need to process every transaction separately so that things are simple. The only thing that I don't know what to do with is a notification

@mandar-brave
Copy link

Updated spec;

  • keep each a/c and tips separate; convert all a/c values to tips once creator-XX is verified
  • when a new publisher is verified, notify once that a publisher is verified "We will send your contributions to newly verified creator-XX" - action OK and close
  • Try sending every tip based on time sequence, FIFO
  • if tips fail, keep them in pending log at the browser till successful
  • if tips fail due to lack of funds, notify first time ONLY when users retry that "You have pending tips due to insufficient funds" - action " Add funds" and drives to add-funds and close
  • (Re) try every day

Each of the notifications ONLY the first time; one time for every verified publisher and one time only for failed retries due to lack of funds.

cc @NejcZdovc

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Jul 15, 2019

Verification passed on

Brave 0.67.108 Chromium: 75.0.3770.100 (Official Build) beta (64-bit)
Revision cd0b15c8b6a4e70c44e27f35c37a4029bad3e3b0-refs/branch-heads/3770@{#1033}
OS Windows 10 OS Version 1803 (Build 17134.523)

image

  • Verified that Tips are processed after the publisher becomes verified and tips are removed from Pending Contribution list
  • Verified the Insufficient funds notification, when wallet balance is less than the Tip amount
    image
    image
  • Verified that the Auto Contribute, One-time Tip, Recurring Tip are removed from pending list when publisher becomes verified
  • Encountered pending AC values are rounded once publisher verifies - follow up to 3741 #4886
  • Verified that the auto contribute values and recurring tips were removed from the pending list and added to Tips panel as one-time tips once creator becomes verified.

Verification passed on

Brave 0.67.110 Chromium: 75.0.3770.100 (Official Build) beta(64-bit)
Revision cd0b15c8b6a4e70c44e27f35c37a4029bad3e3b0-refs/branch-heads/3770@{#1033}
OS Ubuntu 18.04 LTS

image

  • Verified that Tips are processed after the publisher becomes verified and tips are removed from Pending Contribution list

image

  • Verified that the Auto Contribute, One-time Tip, Recurring Tip are removed from pending list when publisher becomes verified
  • Verified that the auto contribute values and recurring tips were removed from the pending list and added to Tips panel as one-time tips once creator becomes verified.

Verified passed with

Brave 0.67.112 Chromium: 76.0.3809.62 (Official Build) beta (64-bit)
Revision 7b77856b3aa34d72f246d12340fc1ded8b2c0e83-refs/branch-heads/3809@{#798}
OS Mac OS X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants