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.
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
RUMM-1779 Keep view active until all resources are consumed #702
RUMM-1779 Keep view active until all resources are consumed #702
Changes from all commits
8a17f5c
92a8105
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This test looks good 👍, although we could also test that "SDK doesn't send view updates to completed views (to ones which received their terminal,
view.isActive == false
update)". How about enhancing session-level validators inRUMSessionMatcher
to also integrate this assertion? It already has the notion ofViewVisit
aggregating all view updates in their time order and even applying some preliminaryisActive
checks.We use
RUMSessionMatcher
in all integration and many unit tests, so this validation would be heavily applied.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.
Yes, I can have a look!
So we would basically stop sending view updates once the view is inactive?
What is the actual definition of an
active
view?I worry if BE start processing inactive view events in the future, we will loose data.
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.
This is exactly how I understand it 👍, but maybe @xgouchet can confirm this.
I will share more context on Slack.
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.
I need further modification to actually prevent from sending update events after a view is inactive, here it just setsis_active: false
It's actually already done here, so it's just a matter of asserting this in test as you mentioned!