Fix NDVR recording timestamp parsing crashing on numeric epoch values#93
Merged
Conversation
The recording detail API returns startTime/endTime as epoch seconds (numbers), but _process_ndvr_state assumed ISO-8601 strings and called .replace() on them, causing an AttributeError. This left duration, show_title, media_type and image unset for recordings. Add _parse_timestamp helper that handles both numeric epochs and ISO-8601 strings with safe fallback.
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
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.
The recording detail API returns startTime/endTime as epoch seconds (numbers), but _process_ndvr_state assumed ISO-8601 strings and called .replace() on them, causing an AttributeError. This left duration, show_title, media_type and image unset for recordings.
Add _parse_timestamp helper that handles both numeric epochs and ISO-8601 strings with safe fallback.