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

🐛 [RUMF-71] prevent negative performance timing duration #246

Closed
wants to merge 3 commits into from

Conversation

BenoitZugmeyer
Copy link
Member

Prevent negative performance timing by liming it to 0. Also filter out timings with invalid start values ('redirect' and 'ssl' generalization).

@BenoitZugmeyer BenoitZugmeyer requested a review from a team as a code owner January 29, 2020 22:39
@BenoitZugmeyer BenoitZugmeyer force-pushed the benoit/fix-negative-durations branch from 50bf9c2 to 15838e3 Compare January 29, 2020 22:48
@BenoitZugmeyer BenoitZugmeyer force-pushed the benoit/fix-negative-durations branch from 15838e3 to b739cbc Compare January 29, 2020 22:49
if (start <= 0) {
return undefined
}
return { duration: msToNs(Math.max(end - start, 0)), start: msToNs(start) }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not so sure about doing this fix right now.

I would be in favor collecting info to understand better the issue and then discuss with the product what is the best way to handle it. We could prefer to not send the timing instead of setting the duration to 0.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I opened #251 for this.

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

Successfully merging this pull request may close these issues.

2 participants