Opened 5 years ago

Closed 5 years ago

#12103 closed Bug Report - General (Fixed)

Metadata library will pull an inetref from ttvdb.py, and then pull data for that inetref from tmdb3.py

Reported by: Stefan Pappalardo <stefan.pappalardo@…> Owned by: Raymond Wagner
Priority: minor Milestone: 0.27.4
Component: MythTV - Mythmetadatalookup Version: 0.27-fixes
Severity: medium Keywords: tmdb3.py crash
Cc: Ticket locked: no

Description

MythTV Version : v0.27-188-g036a336

Reproduction of the crash with: $ /usr/share/mythtv/metadata/Movie/tmdb3.py -l en -a US -D 99151

See attached crash file from /var/crash for details.

See also bug on launchpad: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1236657

Attachments (1)

_usr_share_mythtv_metadata_Movie_tmdb3.py.1000.crash (19.6 KB) - added by Stefan Pappalardo <stefan.pappalardo@…> 5 years ago.
crash file from /var/crash/

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by Stefan Pappalardo <stefan.pappalardo@…>

crash file from /var/crash/

comment:1 Changed 5 years ago by Raymond Wagner

Resolution: Invalid
Status: newclosed

TheMovieDB does not have a movie registered to the IDs 99151 or 266092. At best, I could give you a more human-readable error code, but there's really nothing to fix here.

comment:2 in reply to:  1 Changed 5 years ago by Stefan Pappalardo <stefan.pappalardo@…>

Resolution: Invalid
Status: closednew

Replying to wagnerrp:

TheMovieDB does not have a movie registered to the IDs 99151 or 266092. At best, I could give you a more human-readable error code, but there's really nothing to fix here.

Did you see the crash report from apport in the attachment? In my opinion there is no need for a human-readable error code. Instead I would recommend to add an error handling to prevent the crash.

comment:3 Changed 5 years ago by Raymond Wagner

Resolution: Invalid
Status: newclosed

You're requesting data for an ID that does not exist. That is a fatal error. Whether the exception is handled or not, that's the end of the script. There is nowhere further to go. Handling the exception is a purely cosmetic issue.

comment:4 Changed 5 years ago by Stefan Pappalardo <stefan.pappalardo@…>

Resolution: Invalid
Status: closednew

Further investigation shows that mythmetadatalookup does the failure. It uses tmdb3.py instead of ttvdb.py, although there is a season number / episode number > 0. Is there a way to move the bug to another component? And which component should we choose for mythmetadatalookup?

comment:5 Changed 5 years ago by Raymond Wagner

Component: Bindings - PythonMythTV - Mythmetadatalookup
Milestone: unknown0.28
Status: newassigned
Summary: MythTV.tmdb3.tmdb_exceptions.TMDBRequestInvalid: Invalid id - The pre-requisite id is invalid or not found.Metadata library will pull an inetref from ttvdb.py, and then pull data for that inetref from tmdb3.py

This is a known issue that has come up a couple times before on the mailing list. I thought there was already a ticket open for it, but I've not found it.

comment:6 Changed 5 years ago by Frank Phillips <fphillips81@…>

Fixed by #12149, please close.

comment:7 Changed 5 years ago by Raymond Wagner

Milestone: 0.280.27.4
Resolution: Fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.