-
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
5% fee not always sent #7425
Labels
bug
feature/rewards
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Milestone
Comments
NejcZdovc
added
the
priority/P1
A very extremely bad problem. We might push a hotfix for it.
label
Dec 17, 2019
@NejcZdovc @rebron any updates on this one? It's labelled as a |
Removed from 1.2.x milestone. Need to investigate this one a bit more. |
32 tasks
masparrow
added a commit
to brave/brave-core
that referenced
this issue
Jan 15, 2020
Resolves brave/brave-browser#7425 Browser test Update
Verified passed with
Verification passed on
Verification passed on
Verified the test plan from the description |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/rewards
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Description
If you tip several sites in quick succession, before the 5% is deducted for each one, the 5% will not be sent. 5% is only sent for the last site tipped.
Steps to Reproduce
--rewards=staging=true --brave-ads-staging --enable-logging=stderr --vmodule=*rewards*=6 --log-level=2
A
in screenshot).Actual result:
Expected result:
5% fees to be sent even when tipping in rapid succession
Reproduces how often:
easily
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
Reproduced several times
cc @NejcZdovc @brave/legacy_qa
The text was updated successfully, but these errors were encountered: