Avoid sending latency immediately after the monitor starts #630
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.
Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL: https://app.asana.com/0/0/1206412872188595/f
iOS PR: duckduckgo/iOS#2368
macOS PR: duckduckgo/macos-browser#2103
What kind of version bump will this require?: Patch
Description:
This PR fixes a bug in the latency monitor. See parent task for more info.
Steps to test this PR:
NetworkProtectionLatencyMonitor
line 117 to print when the app is reporting latency backlet reportThreshold: TimeInterval
line to use 1 minute instead of 10 minutesIf you want to test this behaviour before, simply comment out line 95 and test again - you will see that the app is sending its very first measurement as a pixel, instead of collecting an average.
OS Testing:
Internal references:
Software Engineering Expectations
Technical Design Template