Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#7282 closed defect (wontfix) doesn't like Doctor Who

Reported by: mythtv@… Owned by: Anduin Withers
Priority: minor Milestone: unknown
Component: Plugin - MythVideo Version: head
Severity: low Keywords:
Cc: Ticket locked: no


When performing a TVDB metadata search for "Doctor Who", fails with the following:

/usr/local/share/mythtv/mythvideo/scripts/ -D 76107 Traceback (most recent call last):

File "/usr/local/share/mythtv/mythvideo/scripts/", line 1243, in <module>


File "/usr/local/share/mythtv/mythvideo/scripts/", line 1069, in main

seriesfound=searchseries(t, opts, series_season_ep)

File "/usr/local/share/mythtv/mythvideo/scripts/", line 503, in searchseries

seriesfound=search_for_series(t, series_name) # Series only

File "/usr/local/share/mythtv/mythvideo/scripts/", line 482, in search_for_series

return tvdb.series_by_sid(sid_or_name)

File "/usr/local/share/mythtv/mythvideo/scripts/", line 473, in _series_by_sid


File "/usr/local/share/mythtv/mythvideo/scripts/ttvdb/", line 643, in _getShowData

epsEt = self._getetsrc( self.configurl_epInfo? % (sid) )

File "/usr/local/share/mythtv/mythvideo/scripts/ttvdb/", line 427, in _getetsrc

et = ElementTree?.fromstring(src)

File "<string>", line 86, in XML

SyntaxError?: no element found: line 1, column 0

Works ok for everything else, so I'm assuming there is something in the data returned which it doesn't cope with.

Running SVN 22350.

Change History (2)

comment:1 Changed 12 years ago by robertm

Resolution: wontfix
Status: newclosed

Same query works fine here-- A retry (or, failing that, a couple retries) should work. This is more likely related to an issue with the upstream python library not dealing well with multiple queries running at once. We have submitted debug information upstream but until the author comes out with a fix, I am left recommending that you retry. Failing that, in an extreme scenario you may need to clear your tvdb_api cache with:

rm -rf /tmp/tvdb_api_*

I am hoping to have a fix from upstream soon, but as the issue doesn't exist in code we control, I am closing this wontfix for now.

comment:2 Changed 12 years ago by mythtv@…

Thanks for that... it looks like it was corrupted data in the tvdb_api cache. I cleared it out, and it's all good now.

I suspect that this particular one caught me out because it was so big and took ages to return. I'll just have to learn some patience.

Note: See TracTickets for help on using tickets.