-
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
Stats updater uses wrong timestamps #3895
Comments
@bbondy @too4words @aekeus JFYI |
Also there is a possible underflow: https://github.com/brave/brave-core/blob/master/browser/brave_stats_updater_params.cc#L98 ( |
I guess I ported this bug right over from Muon, oops: https://github.com/brave/browser-laptop/blob/8692beec44ff4a0a7c56b5ba004bc6ea75365ccf/app/dates.js#L42 |
Verification passed on
Used test plan from brave/brave-core#2112 Verified passed with
Initial ping: "Next Day" ping: Verification passed on
Initial ping: "Next Day" ping:
|
https://github.com/brave/brave-core/blob/master/browser/brave_stats_updater_params.cc#L17
Here we cache
base::Time::Now()
on startup and then use it in all outgoing pings. This way, all stats updater pings contain the same timestamp until the browser restart.It would be more precise to take the actual
Now()
every time.Brave | 0.64.2 Chromium: 73.0.3683.75 (Developer Build) (64-bit)
The text was updated successfully, but these errors were encountered: