-
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
Only add jitter for Brave Ads token redemption when creating the timestamp #9624
Comments
Verification passed on
Verified test plan from brave/brave-core#5461 Verified "Payout tokens" date in the console log does not change between browser relaunche
On second launch
Verified Payout tokens date changes as time passes by.
Verified dates are on average ~24 hours. @tmancey mentioned that each date can be in range from 1minute to 72hours or more. Average is 32 hours Verification passed on
Verified test plan from brave/brave-core#5461 Verified "Payout tokens" date in the console log does not change between browser relaunch
second launch
Verified Payout tokens date changes as time passes by.
Verification PASSED on
Verified the STR/test plan outlined via brave/brave-core#5461 Verified "Payout tokens" date in the console log does not change between relaunches as per the following: On initial browser launch
On second launch
Verified Payout tokens date changes as time passes by and tokens are paid out on the correct date as per the following:
Ensured that once the token payout occurs, the next payout time is set:
|
Description
Only add jitter for Brave Ads token redemption when creating the timestamp
Steps to Reproduce
Actual result:
Token redemption date changes when relaunching the browser due to a different jitter being added to the date each time the payout tokens timer is started
Expected result:
Payout token date should not change between browser relaunches
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: