Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

address kodi review comments + catch missing epg time markers #24

Merged
merged 9 commits into from
Nov 1, 2020

Conversation

piejanssens
Copy link
Collaborator

No description provided.

@piejanssens piejanssens merged commit 88c6bea into add-ons:master Nov 1, 2020
@dagwieers
Copy link
Contributor

Everything is working fine here ;-)

item.get('start_time')
and item.get('end_time')
and re.match('\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}.\d{3}Z', item.get('start_time')) # pylint: disable=anomalous-backslash-in-string
and re.match('\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}.\d{3}Z', item.get('end_time'))): # pylint: disable=anomalous-backslash-in-string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I'd we can have missing start/end times that we need to catch, maybe also catch incorrect/different time stamp formats. I have not seen any though. We should log this at INFO level I think.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not concerned about this, obviously we need to protect against missing entries and check the routine to report this in GitHub CI whenever this would happen. But I wouldn't handle this specifically in the add-on itself just yet. This is not very efficient.

So I would let it die with an exception for conditions we don't expect to happen. Otherwise we may not know about them if they do happen and they are not "in your face". Let's work on a Status workflow that also runs this code path to ensure that it is safe to use.

@dagwieers dagwieers added this to the v3.2.1 milestone Nov 4, 2020
@dagwieers dagwieers added bug Something isn't working release Related to release management labels Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release Related to release management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants