fix: clamp negative values from the Ookla CLI - #2868
Merged
Conversation
alexjustesen
approved these changes
Aug 16, 2026
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
2 participants
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.
📃 Description
As offered in #2864. The decoded CLI output runs through a small clamp before anything is stored, so the mapped columns and the same fields inside
datastay consistent — ping latency, bandwidth and bytes in both directions. Nulls and missing fields pass through untouched so a failed metric doesn't turn into a fake zero, and everything else in the json is left as the CLI reported it. Only new results are guarded, existing rows aren't rewritten.Closes #2864
🪵 Changelog
🔧 Fixed