[mythtv-commits] Ticket #12612: New installs die after a few days fixes/0.27 (v0.27 (v0.27.5-71-ga62fc0d)

[MythTV]

#12612: New installs die after a few days fixes/0.27 (v0.27 (v0.27.5-71-ga62fc0d)
----------------------------------+--------------------------------
 Reporter:  singogli@…            |          Owner:
     Type:  Bug Report - General  |         Status:  infoneeded_new
 Priority:  minor                 |      Milestone:  unknown
Component:  MythTV - General      |        Version:  0.27.5
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+--------------------------------

Comment (by singogli@…):

 Responding to dekarl:
 Yes the offending byte was the last of the string.  I have attached the
 mysql string as a file: offending_channel_string.  Indeed this was a US
 ATSC channel.

 As I recall this problem occurred with the original build using
 schedulesdirect and another attempt using the OTA data but I don't recall
 if the OTA attempt was a fresh install or just changing the setup option.
 I don't know if changing the option would purge the bad byte/character? If
 I had to guess I would say both th OTA and the schedulesdirect data
 contain the bad byte.

 Wouldn't it be a good idea to validate all 3rd party data streams and
 strip all unneeded null bytes?

 Are there any published specification for this data?  Should I notify the
 station or schedulesdirect?

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12612#comment:14>
MythTV <http://www.mythtv.org>
MythTV Media Center