This repository was archived by the owner on Nov 24, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 356
Draft
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Traffic Monitor logs kept throwing a warning for speed whose value wasn't in the int range
WARNING: stats_over_http.go:319: 2023年07月06日T04:01:42.26864894Z: speed of interface 'p1p1' cannot parse to int64, was '18446744073709551615': strconv.ParseInt: parsing "18446744073709551615": value out of rangeWhich Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Ensure that the warning message is no longer seen in the logs.
If this is a bugfix, which Traffic Control versions contained the bug?
7.0.1
PR submission checklist