Unraid PMM docker looking for playlist_files in config.yml but it isn't required

[tribal stream]

Welcome @marble yacht!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

You can press the "Close Post" button above or type /close at any time to close this post.

[tribal stream]

Hi - I last completed a run of PMM successfully @ noon today (25 Apr 2024) but since v2 was released an hour ago, I can no longer successfully complete a run. I've attached a copy of my log and config.yml file

[ember spire]

It's not the playlist_files thing causing this error. It's failing when attempting to load some anime data:

|     self._anidb_ids = self.config.get_json(anime_lists_url)                                        |

[marble yacht]

Oh, thanks for the info! Any idea what that is?

I just saw the traceback after looking for playlist_files and assumed that was it

[ember spire]

It's retrieving:

https://raw.githubusercontent.com/Kometa-Team/Anime-IDs/master/anime_ids.json

And is receiving invalid JSON:

| requests.exceptions.JSONDecodeError: Extra data: line 1 column 4 (char 3)                          |

But if I retrieve that and feed it into a JSON linter it's fine.

Maybe a transient issue? try it again.

[marble yacht]

Ok I'll give it another go

nope, same issue

[ember spire]

oh, wait, you're not running Kometa

[marble yacht]

this is meisnate12/plex-meta-manager:latest

I'm using the PMM meisnate unraid docker

[ember spire]

Yeah, your script is attempting to load:

https://raw.githubusercontent.com/meisnate12/Plex-Meta-Manager-Anime-IDs/master/pmm_anime_ids.json

which no longer exists

[marble yacht]

Oh ok. So then the current unraid docker will no longer function, correct?

[ember spire]

Appears so. You could manually edit the file inside the container to replace that URL.

[marble yacht]

Ok. I don't know how to do that, so I will switch to Kometa 🙂 . Can this be documented in rebrand-guidance though? On reddit, it's out there that this rebrand isn't a breaking change to current configs

[ember spire]

I'm not sure this was intentional

I've alerted the team

[marble yacht]

Oh I don't think it was intentional at all. But if the current unraid docker doesn't work now, I think that's worth noting

Thanks!

I close the thread now, thanks for being super responsive and for the detailed explanation on what was going wrong