-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix: make android samples monotonic #337
Conversation
timestamps (in this case just seconds) into a monotonic one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if the Nanos
part of the clock is having this behavior? Shouldn't we take care of the whole clock?
@phacops I don't know if this can happen. |
I've changed the logic to convert This will take care of everything and it's more appropriate than treating them independently. |
Loop once, if the condition is detected then break and loop again starting from that index applying the logic to fix the time without checking the condition each time
Wall-clock time is supposed to be monotonic. In a few rare cases we've noticed this was not the case.
Due to some overflow happening client-side in the embedded profiler, the sequence might be decreasing at certain points.
This is just a workaround to mitigate this issue (at rendering time) and avoid a front-end crash, should it happen.