Don't log downsample warning when unnecessary #4291
Merged
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.
Why
The logic that is logging errors in dev mode for a missing entry in
DOWNSAMPLED_EVENTS
gets logged any time thatisDownsampledSession
is true - which is most often since there's a 90% chance of downsampling, since there is no.has
check before the log, just a check forendsWith
.I've fixed that, as well as moved this log above the
isDownsampledSession
check, so we are sure to get an error rather than possibly missing it if we get the 10% chance of a downsampled session.Test Plan
Open the app, see that there is no longer an error displayed when viewing the home tab. You can invert the check on line 108 to see that the logs do still show up in dev mode.