[RUM-9151]: fix issue with missing freeze rate and slow frames rate#2557
Merged
Conversation
0xnm
previously approved these changes
Mar 19, 2025
0xnm
approved these changes
Mar 19, 2025
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2557 +/- ##
===========================================
- Coverage 70.23% 70.16% -0.08%
===========================================
Files 803 803
Lines 30196 30197 +1
Branches 5059 5060 +1
===========================================
- Hits 21207 21185 -22
- Misses 7590 7598 +8
- Partials 1399 1414 +15
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Changes logic for ui slowness report a bit: now report is removed only when view is complete
Motivation
We have an issue with
resolveReportmethod implementation: report was removed from the map whenresolveReportis called, so in case if there are several events within the view scope - report will be sent only for the first updateAdditional Notes
These changes should be part of the main feature branch PR but it was too big so I've decided to merge them separately
Review checklist (to be filled by reviewers)