Fix issue in pace timeline with no moving time #23
Conversation
This file contains 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
Sometimes the "moving time" of an activity is broken in Strava. Typically for very old Garmin uploads, this field is either zero or way too large. If it is zero, when we resample to create the moving average lines, we can divide by zero, and get extra NaN's and then filter them out. Very niche issue, but this takes care of it + adds a test to make sure we don't regress.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes the "moving time" of an activity is broken in Strava. Typically for very old Garmin uploads, this field is either zero or way too large. If it is zero, when we resample to create the moving average lines, we can divide by zero, and get extra NaN's and then filter them out. Very niche issue, but this takes care of it + adds a test to make sure we don't regress.