#top 10 unwatched

1 messages · Page 1 of 1 (latest)

glad vector
#

I did have this working, but the list i was following stopped updating. so I just tried a new list and apparently its broken now.

Goal:

  1. call up a list of the most popular movies - Get the top 100 movies from this list and only display 10
  2. add an overlay
  3. Once I have watched a show, the overlay is removed and it's replaced on the list by the next up.

Actual outcome:

  1. working
  2. working
  3. despite watch status, the movies don't change
faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#

Welcome @glad vector!

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

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

#

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

deep horizon
#

wow, first update your PMM, you are on 1.17 and we are now on 1.19.1

hazy emberBOT
#

NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.

The update method depends on how you installed it.

I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.

This is the "fussiest" method of update.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].

I'm using docker on a NAS or some other remote context:

Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.

glad vector
#

Well that’s embarrassing.

#

Anything else in the log tho you think might be bad?

storm dirge
#

Please update and run... then drop logs here and have luma logscan scan it by clicking the white check when prompted.

#

All the most critical recommendations will be at the top...

glad vector
#

what do you mean by critical recommendation? Log coming in hot in like 2 min.

faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**PMM Config.yml YAML Validation** ❌
YAML Validation Results

INVALID YAML detected

INVALID YAML content

while scanning a block scalar
in "<unicode string>", line 147, column 65:
... | settings sub-attribute show_un ...
^
expected a comment or a line break, but found 's'
in "<unicode string>", line 147, column 67:
... | settings sub-attribute show_unco ...
^

glad vector
#

I'm sorry i'm not sure what all this means @storm dirge . does anything here stand out to you?

storm dirge
#

Yes the topmost issue is a problem where basically your yaml is not valid

#

Page 4

glad vector
#

oh no. how do I go about this fix? should i drop in here too?

storm dirge
#

You have issues with your config from what this shows

#

No

#

1 sec

glad vector
#

ok, thank you very much!

storm dirge
#

I will need to rerun the logscan because you did not extract the config... 1 sec

faint crescentBOT
#

📝 If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

faint crescentBOT
# faint crescent
**User Info**

Author of Linked Message: Yello0wKing
Person who Invoked the Command: bullmoose
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - ❌ ANIDB AUTH ERRORS
Page 08: Rec 02 - ❌🔒 BLANK API KEY ERROR
Page 09: Rec 03 - ❌ [ERROR]
Page 10: Rec 04 - ❌ MY ANIME LIST CONNECTION ERROR
Page 11: Rec 05 - ❌ METADATA LOAD ERRORS
Page 12: Rec 06 - ❌ OVERLAY LOAD ERRORS
Page 13: Rec 07 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 14: Rec 08 - ⚠️ [WARNING]
Page 15: Rec 09 - 💬 OLD PMM YAML
Page 16: Rec 10 - 💬💡️ PLEX DB CACHE ADVICE

faint crescentBOT
storm dirge
#

You have an empty metadata_path section

glad vector
#

oh got it, i think thats for the tv section, tho, no?

storm dirge
#

Search for - git: PMM/chart/ and replace with - pmm:

hazy emberBOT
#

- git: PMM/...

Using - git: PMM has been replaced in 1.18.0 with - pmm:, we recommend updating any references to - git: PMM.

Please type !118 for further information.

glad vector
#

oh ok! I'm doing so now.

storm dirge
glad vector
#

should i re-run after replacing? and drop a new log?

storm dirge
#

Yes

glad vector
#

on it- thank you very much!

storm dirge
#

And answer yes to both prompts please

glad vector
#

ok!

faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 09** - 💬 **OLD PMM YAML**

💬 OLD PMM YAML
You are using an old config.yml with references to metadata files that date to a version of PMM that is pre 1.18
In the PMM discord thread, type !118 for more information.
For more information on handling this, [https://www.metamanager.wiki/en/latest/config/configuration.html]
1 line(s) with OLD PMM YAML. Line number(s): 73

glad vector
#

@storm dirge looks like it finished with a Check mark on page 4 now!

storm dirge
#

So it seems that you may also be using folders that contain yml files in them?

#

I see the use of - folder:

glad vector
#

yes - honestly i'm not very good at this, so i appreciate you helping. I have a separate folder which has ymls in them. Here's the one with the top 10 unplayed stuff.

faint crescentBOT
#

YAML checked and is NOT valid. Error message:

while parsing a block mapping
in "<unicode string>", line 5, column 3:
Top 10 Today:
^
expected <block end>, but found '<block mapping start>'
in "<unicode string>", line 9, column 5:
sync_mode: sync
^

storm dirge
#

Also, look at line 73 in your log file, looks like old yml references there as per luma

#

There you go... that file has invalid yml. Where did you get that file from?

#

And we strongly suggest using a good editor... free of course...

hazy emberBOT
#

We highly recommend to use a decent editor software to manage PMM's .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in PMM.

This can save a lot of time and headaches.

Visual Studio Code (Windows/Mac/Linux, Opensource & Free)
Website

Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look here.

glad vector
#

from a separate folder, how you'd referenced. does that one have the same replacement stuff? I have notepad ++ is that ok?

storm dirge
#

We suggest vscode

#

With indent rainbow plug-in

glad vector
#

ok! before switching that over, is there something you see i should change in the top 10 yml? im not sure what that error means.

storm dirge
#

I have no context on how you got here and what state things were in.. and I can't look into your machine. So the more information you share, the clearer the picture becomes

#

Basically... we need to get you up and running and then work on the extra stuff you have. So comment out the folder for now

glad vector
#

so on the config yml, add a # infront of the movies metadata_path and drop in a new log, right?

storm dirge
#

No.. in front of the line with - folder

glad vector
faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 08** - 💬 **OLD PMM YAML**

💬 OLD PMM YAML
You are using an old config.yml with references to metadata files that date to a version of PMM that is pre 1.18
In the PMM discord thread, type !118 for more information.
For more information on handling this, [https://www.metamanager.wiki/en/latest/config/configuration.html]
1 line(s) with OLD PMM YAML. Line number(s): 73

storm dirge
#

Page 14

#

Please read and address

glad vector
#

reading now!

storm dirge
#

So scroll to line 73 in the meta.log and what is there?

glad vector
#

So, line 73 for me is: "timeout: 60" when i go to the link in there, it shows that in the example

storm dirge
#

Line 73 in meta.lig

glad vector
#

oh, woops. looking now

#

i missed one - git: PMM. re-running

faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 05** - ❌ **OVERLAY LOAD ERRORS**

OVERLAY LOAD ERRORS
Plex Meta Manager is trying to load a file from your config file.
This error indicates that the setting is not correctly setup in config.yml. Usually wrong path to the file, or a badly formatted yml file.
Within the attached log file, go to the indicated line(s) for more details on the exact issue and take actions to fix.
For more information on this, [https://www.metamanager.wiki/en/latest/config/configuration.html]
2 line(s) with OVERLAY LOAD errors. Line number(s): 265, 270

glad vector
#

@storm dirge looks like that one's gone now

glad vector
# faint crescent

@lyric jackal looks like bullmoose had to drop offline, and i see your online. any chance you might be able to assist, or do you think i should wait til tomorrow/later. thank you again foe everything!

storm dirge
#

Page 11

#

You should probably also be on develop branch

hazy emberBOT
#

NOTE: This is addressing changing from, for instance, latest to nightly.

The method depends on how you installed it.

**I'M USING DOCKER:**
docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as meisnate12/plex-meta-manager:TAG_HERE

**I'M USING DOCKER ON UNRAID**

:one: Click on DOCKER tab and then on Plex-Meta-Manager
:two: Edit Repository: setting to switch branches:

meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

**I'M USING DOCKER ON A SYSTEM WITHOUT COMMAND PROMPT (SUCH AS NAS):**

The same concepts as above will apply:
:one: pull new image
:two: recreate container using that image instead of the current one.

Whatever the system, there will be a way to accomplish these two things.

**I'M RUNNING LOCALLY VIA GIT:**
cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

storm dirge
#

Set your db_cache: 1024 within the Plex section of your config.yml

#

Do you have anime? If not get rid of that from your config.

glad vector
#

ok! on it!

storm dirge
#

Lines 265 and 270 in the meta.lig are referencing overlays. We need to understand why those are failing

#

Two of those files are empty. Just remove them completely as they serve no purpose

glad vector
#

ok!

storm dirge
#

lol

#

Did you ever have this working?

glad vector
#

i did. lol. and i loved it and told everyone how it was awesome and they were like "howd you do it?" and i said... i don't know. lol

storm dirge
#

Ok. Well we will get it all back.

#

Eventually

#

K... gotta go!

glad vector
#

ok! is it ok if we pick up tomorrow?

faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**User Info**

Author of Linked Message: Yello0wKing
Person who Invoked the Command: Yello0wKing
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - ❌🔒 BLANK API KEY ERROR
Page 08: Rec 02 - ❌ [ERROR]
Page 09: Rec 03 - ❌ MY ANIME LIST CONNECTION ERROR
Page 10: Rec 04 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 11: Rec 05 - ⚠️ [WARNING]

glad vector
faint crescentBOT
#

📝 If you want to review this again, yello0wking:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 01** - ❌ **[ERROR]**

[ERROR]
Error messages found in your attached log.
There is a very strong likelihood that PMM did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://www.metamanager.wiki/en/latest/home/kb.html#error]
3 line(s) with [ERROR] messages. Line number(s): 227, 255, 808

storm dirge
#

Set your Plex maintenance end time to 5am and that error will go away

#

Looks like you also are trying to use MAL. MyAnimeList... so again if anime is not needed then remove/comment.

#

Different people here in the PMM community will contribute to solving the issues you are facing so generally, if I don't answer, there are others... and it's just a question of being a little patient and things will get solved.

glad vector
#

hey again! im down to just a few errors last scan i ran, but i feel like i have a syntax issue or something with this one.

pliant oasis
#

What makes you feel that way?

glad vector
#

I’m not really sure it’s kind of just a feeling which doesn’t get me very far. I think number one. The list is an updating anymore. Number two it’s definitely not filtering out items I’ve played once.

pliant oasis
#

The log should reveal what PMM is doing and why. It does seem odd to retrieve 100 things then ignore 90 of them.

#

Is it not updating, or not changing?

glad vector
#

Totally open to ideas.
My thought is “I only care about the top things I haven’t seen” so I need a bigger list to pull from, or the top 10 becomes a top 7 if I watched 3 of em.

Do you know of any better lists than maybe the one I’m using?

pliant oasis
#

Why do you need an external list? Why not just sort the unplayed movies already in your library by some sort of rating and show the top ten? I imagine the external list contains a lot of stuff not in your library, which is maybe why you were retrieving so many?

pliant oasis
#

Maybe something like:

collections:
  Top 10 Unplayed:
    collection_order: custom
    plex_search:
      all:
        unplayed: true
        critic_rating.gt: 6
      sort_by: critic_rating.desc
      limit: 10
glad vector
#

interesting... i think i was goong down that line cause if i used your lines above i'd get results like from 1950 for movies that are classics i havent seen. im hoping to keep it to newerish stuff. any other filters you think i should drop in?

pliant oasis
#

Then add criteria to limit the age.

glad vector
#

reading through The wiki i didnt see many relative references. any ideas to keep the info current? like released before: current_month-2

pliant oasis
#

Maybe something like:

collections:
  Top 10 Unplayed from the last 5 years:
    collection_order: custom
    plex_search:
      all:
        release: 1825 # 5 years is 1825 days
        unplayed: true
        critic_rating.gt: 6
      sort_by: critic_rating.desc
      limit: 10
storm dirge