guard against undefined previousValue on first network reading - #578
Merged
corecoding merged 2 commits intoAug 16, 2026
Merged
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 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.
Small one.
values.jsreadspreviousValue[1]before checking there is a previous value,so the first time an interface shows up it throws:
The
.catchinsensors.jsswallows it, so all you see is one missing reading for thatinterface. Not a big deal on its own, but it happens for every new interface, which adds up
with docker or a VPN.
Guarded with a ternary.
Together with #577 this also sorts out the negative speeds in #545. That one needs both, so
I've left the closing keyword off it.