Fixing panic seen in TM when timestamp_ms appears as float and not string #7730
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.
Resolving the panic seen in a stack trace.
Aug 17 16:53:29 : panic: interface conversion: interface {} is float64, not string
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Run unit tests and when installing TM in an environment, ensure that it starts up without a panic.
If this is a bugfix, which Traffic Control versions contained the bug?
7.0.1
PR submission checklist