search

JakeLunn / one-pace-plex-assistant

A CLI tool for making the process of importing One Pace episodes into Plex much easier.
14 stars 3 forks source link

Failed to execute script 'main' due to unhandled exception! #19

Open jjnether opened 3 months ago

jjnether commented 3 months ago

Not sure how to troubleshoot this. Any help would be appreciated!

image

jjnether commented 3 months ago

Could this be because the One Pace website is down?

jd4883 commented 3 months ago

@jjnether I have ran into the same issue. I have a pretty slick cronjob that pulls a python docker language image and clones this project from github, then executes it with some additional scripting to clean up files so I was also disappointed when I realized my scripting setup which has worked for close to a year was not behaving. When I read my logs in my cronjob, I saw similar json decode errors.

Looking at how the code works I'm fairly sure it pulls data from a fixed set of links from onepace.net. However, the site is either in a long-standing maintenance mode or may be replaced by something entirely different (reading through the notifications in the discord without going too far back) I know they are switching the streams to pixeldrain, what I don't know is if the website frontend that they used to have will come back. If you aren't following the discord, you can join and get release info from here https://linktr.ee/onepaceproject. onepace.net simply gets you to the discord link now and does not load a front end. Per this FAQ, it implies the website will be back and if so it's unlikely they would restructure the underlying links thus breaking the script. But when the frontend website is back up remains to be seen. The post was from 7/1/24 so it's been down almost a month.

Presumably, if onepace.net will be coming back to life as a front end, I would presume all the python code written in this project, provided the hierarchy remains the same and the underlying images live in the same locations, the script will again work.

If I am wrong though on any of my assessments I'd be interested to know more.

If there are other insights or troubleshooting data that can be provided I'm happy to assist. While I am not a contributor to this project, I have read through the source code a few times and have a reasonably decent idea of how the components are able to work. From what I can tell, my conclusion is that the onepace.net site being functional and having mappings to where metadata can be pulled that maps to said metadata (i.e. the website has to be up and functioning as it used to), then it should start working.

jjnether commented 3 months ago

@jd4883 Appreciate the response. I think the problem definitely is because of the website being down. In the meantime, I ended up using the resources from this repository to get my setup working.

paulkugener commented 2 months ago

@jjnether Could you give more information on your solution? Did you modify OPPA to use information from the linked repo or did you use the whole setup from the other repo?

jjnether commented 2 months ago

@jjnether Could you give more information on your solution? Did you modify OPPA to use information from the linked repo or did you use the whole setup from the other repo?

I ended up just entirely using the other repo. It's quite simple to get going, you just need to use the rename tool to properly name everything, install the XBMC nfo importer tool for TV shows, then use that as the metadata agent after moving all the .NFO's to the proper directories.

StefanLobbenmeier commented 4 days ago

FYI the website is back online, so might be worth checking if endpoint works again.

(Manually inspecting the html I could not see a build id though)