Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
epg: more robust 32-bit object ID handling
Changes:
- store the last id number to the epgdb file
(the purpose is to reuse the id numbers as last as possible)
- use RB tree to track id numbers (faster lookups)
- skip invalid zero IDs (++_epg_object_idx)
- skip used IDs (rare, but possible)
The goal is to handle correctly the 32-bit ID wrapping (++_epg_object_idx).- Loading branch information
Showing
4 changed files
with
84 additions
and
21 deletions.
There are no files selected for viewing
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
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
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
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
1fbbbb8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change seems to completely break recordings. All actually finished recordings are shown as failed (time missed) in webui. Upcoming recordings will not be started...
1fbbbb8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tt's probably caused by 67f5e84 . but new recordings should be fine.. I cannot reproduce here...
1fbbbb8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure which commit broke the recordings, but I had it as well - not all of them, though, some remained scheduled while some upcoming recordings moved to 'Time Missed'. The good news is that it's recoverable: delete the failed recording record, and re-schedule (manually or disable/enable the relevant rule) and they're back again. At least, that seemed to work for me, and I've had two recordings run this morning as scheduled...
1fbbbb8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if you delete/readd the recordings, all should be fine.. If you like to move the logs from failed to finished, just change errors=0 in appropriate files in the /dvr/logs directory..