TypeError: 'NoneType' object cannot be interpreted as an integer | Kometa | Page 1

heady valve Jan 7, 2024, 2:04 AM

#

Hello there.....I've been making some changes to my overlay files but this error may have been happening before...I'm not really sure. The most recent run on this library I'm testing with had 467 episodes to update overlays for, and 162 had this error. Within the same show it will succeed for an episode and fail for the next, and unfortunately I don't understand enough of the code to be able to interpret what the error is telling me, so I would really appreciate some help.

📎 message.txt

bitter galeBOT Jan 7, 2024, 2:04 AM

#

Welcome @heady valve!

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.

bitter galeBOT Jan 7, 2024, 2:04 AM

#

bitter gale You can press the "Close Post" button above or type `/close` at any time to clos...

rare shuttleBOT Jan 7, 2024, 2:06 AM

#

Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯\(ツ)/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

vague shard Jan 7, 2024, 2:06 AM

#

need logs

heady valve Jan 7, 2024, 2:14 AM

#

📎 meta.log

bitter galeBOT Jan 7, 2024, 2:15 AM

#

📝 If you want to review this again, eldoctor6731:
: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 02** - ❌⏰ **PMM RUN TIME > TIME BEFORE MAINTENANCE**

❌⏰ PMM RUN TIME > TIME BEFORE MAINTENANCE
This Run took: 1:50:08
Time between PMM Scheduled time and Plex Maintenance start: 21:00:00
PMM Scheduled start time: 1:00
Plex Scheduled Maintenance start time: 2:00
Plex Scheduled Maintenance end time: 5:00
If your PMM runs typically take this long [this run took 1:50:08], your PMM run time will coincide with the next Plex maintenance period. Consider moving the PMM scheduled start time to 5:00 or adjust the Plex Scheduled Maintenance times to end prior to the PMM Scheduled run time.
For more information on Plex Maintenance, see https://support.plex.tv/articles/202197488-scheduled-server-maintenance/

vague shard Jan 7, 2024, 2:18 AM

#

i'd turn off reapply_overlays

heady valve Jan 7, 2024, 2:19 AM

#

I usually have that off - I only turned it back on to apply the new overlay I was working on

vague shard Jan 7, 2024, 2:19 AM

#

dont need to

#

it will apply automatically

#

the error should be fixed in develop

heady valve Jan 7, 2024, 2:20 AM

#

oh i see....well that's good news. So (maybe a stupid question), what is reapply_overlays actually doing?

calm kernel Jan 7, 2024, 2:20 AM

#

can you switch branches please

rare shuttleBOT Jan 7, 2024, 2:20 AM

#

Moving between branches of PMM

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.

calm kernel Jan 7, 2024, 2:20 AM

#

:develop

vague shard Jan 7, 2024, 2:21 AM

#

heady valve oh i see....well that's good news. So (maybe a stupid question), what is reappl...

telling PMM to apply the overlay whether it needs to or not. pmm will look at the file and will then decide whether it needs to apply an overlay or not

calm kernel Jan 7, 2024, 2:21 AM

#

reapply_overlays: true is applying an overlay regardless of whether there is a change or not

#

so if you go into the poster and bring it up, you porbably have 10-20 duplicate poster files with the exact smae obverlay

#

we call that poster plex bloat

heady valve Jan 7, 2024, 2:22 AM

#

calm kernel can you switch branches please

Which branch do I want?

vague shard Jan 7, 2024, 2:22 AM

#

heady valve Which branch do I want?

#1193374520380235918 message

calm kernel Jan 7, 2024, 2:22 AM

#

look up 3 messages

#

;llol

#

develop

heady valve Jan 7, 2024, 2:22 AM

#

calm kernel look up 3 messages

whoops

#

🙂

calm kernel Jan 7, 2024, 2:22 AM

#

its ok.

vague shard Jan 7, 2024, 2:23 AM

#

and i mentioned long before that lol

bitter galeBOT Jan 7, 2024, 2:24 AM

#

bitter galeBOT Jan 7, 2024, 2:24 AM

#

bitter gale

📎 parsed_meta.log_config_eldoctor.yml

heady valve Jan 7, 2024, 2:24 AM

#

ok switched to :develop, and I'll update to change reapply_overlays to false

calm kernel Jan 7, 2024, 2:24 AM

#

yes, please rerun and just do a Movies run with just overlays

#

python plex_meta_manager.py -rl "TV Requests" -ov

#

oh wait

#

this config file only has TV

#

command adjusted

#

if you had multiple libraries defined in your config.yml file, that would be how you can tell pmm to run 1 specifically

heady valve Jan 7, 2024, 2:27 AM

#

That's good to know - i've been swapping config files to achieve that.

#

This will take some time to run so I'll check on it and update. Thanks for the help so far!

calm kernel Jan 7, 2024, 2:30 AM

#

1:50

#

thats what luma says...

#

almost 2 hours

#

oh boy

#

just saw a recommendation

#

you might want to stop the run

#

actually.. its fine

#

Rec07 is an easy fix that you should make to your config.yml files

#

db_cache: 1024 under the plex settings in your config file could be useful for you

#

oh... pmm is scheduled to run at 1am?

#

Rec02

heady valve Jan 7, 2024, 2:34 AM

#

Yes but I saw that conflict with PMS scheduled activity too so I'm going to change that

calm kernel Jan 7, 2024, 2:35 AM

#

move pmm to 5am is the easiest fix

#

leave plex maintenace to 2-5am which is defaults for them

heady valve Jan 7, 2024, 2:35 AM

#

Sounds good

calm kernel Jan 7, 2024, 2:36 AM

#

btw... develop has some performeance improvements... not sure you will see them on overlays, but definitely for mass_updates and batch edits in collections

heady valve Jan 7, 2024, 2:37 AM

#

That's good. I have some thinking to do about how to handle the overlays. I like them but it seems to really impact the runtime and I have some larger libraries (I was testing this change in the smaller ones first)

calm kernel Jan 7, 2024, 2:41 AM

#

some people run overlays on a schedule like 1 time per week

#

my lib is tiny

vague shard Jan 7, 2024, 2:43 AM

#

my tv, i run overlays only once a week

calm kernel Jan 7, 2024, 2:44 AM

#

and since you are testing... honestl.. creaet a small test library with only 4-5 shows

#

and multuple seasons

#

then you run agains tthat test library

#

when happy... let it rip on your libraries

#

a 2 hour run is pretty annoying

#

well... I dont have the patience for more than 10 minutes

#

but thats me

heady valve Jan 7, 2024, 3:40 AM

#

I did have that for the previous tests but wanted to see if it was a problem with the library. I'll change to the small test library for the next run

#

it's done now, but the errors persist....

#

📎 meta.log

bitter galeBOT Jan 7, 2024, 3:40 AM

#

📝 If you want to review this again, eldoctor6731:
: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 02** - ❌ **MASS_*_UPDATE ERROR**

❌ MASS_*_UPDATE ERROR
You have specified a mass_*_update operation in your config file however you have not configured the corresponding service so this will never work.
Review each of the lines mentioned in this message to understand what all the config issues are.
In the PMM discord thread, type !wiki for more information and search.
For more information on mass_*_update operations, [https://www.metamanager.wiki/en/latest/config/operations.html]
1 line(s) with mass_*_update config errors. Line number(s): 26370

bitter galeBOT Jan 7, 2024, 5:21 AM

#

📝 If you want to review this again, antwanchild:
: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> 📝

bitter galeBOT Jan 7, 2024, 5:22 AM

#

bitter gale

**Rec 02** - ❌ **MASS_*_UPDATE ERROR**

❌ MASS_*_UPDATE ERROR
You have specified a mass_*_update operation in your config file however you have not configured the corresponding service so this will never work.
Review each of the lines mentioned in this message to understand what all the config issues are.
In the PMM discord thread, type !wiki for more information and search.
For more information on mass_*_update operations, [https://www.metamanager.wiki/en/latest/config/operations.html]
1 line(s) with mass_*_update config errors. Line number(s): 26370

bitter galeBOT Jan 7, 2024, 5:22 AM

#

bitter gale

📎 parsed_meta.log_config_eldoctor.yml

vague shard Jan 7, 2024, 5:24 AM

#

your template_variable of overlay level on your own file isn't going to work

clear jolt Jan 7, 2024, 5:43 AM

#

The cause of that error is that some value that the code expets to be an integer is being set to nothing.

All cases of this in the log have one overlay in common:

[2024-01-06 22:03:53,900] [overlays.py:374]           [ERROR]    | Overlays Attempted on Nurse Jackie Season 1: Overlay File (3) 720P

Fortunately there were a few cases where only one this one overlay was being applied where this error occurred; the other 188 all share eight overlays.

They all have Overlay File (3) 720P, though.

I note that you appear to have your own resolution overlay file, so it's apparently going to be something in that custom YAML of yours.

heady valve Jan 7, 2024, 5:31 PM

#

vague shard your template_variable of overlay level on your own file isn't going to work

Why is that?

vague shard Jan 7, 2024, 5:34 PM

#

Template variables are setup for the defaults

heady valve Jan 7, 2024, 5:37 PM

#

📎 resolution_season.yml

#

This is the resolution_season.yml file that's referenced in the config.yml

heady valve Jan 7, 2024, 5:38 PM

#

vague shard Template variables are setup for the defaults

Sorry I don't understand...

real rain Jan 7, 2024, 5:43 PM

#

heady valve Sorry I don't understand...

Template Variables are specifically for the PMM Defaults

#

They can't generally be used for user-created files

clear jolt Jan 7, 2024, 5:52 PM

#

If that file of yours started as a copy of the default file, then you can use template variables. You can't use template variables on any arbitrary metadata file one might create. Unless of course i you I have written it to incorporate them.

heady valve Jan 7, 2024, 5:55 PM

#

The resolution_season file is basically unchanged from what was originally created - I think the only change I made to it was moving the vertical_offset slightly down

clear jolt Jan 7, 2024, 5:56 PM

#

heady valve The resolution_season file is basically unchanged from what was originally creat...

Why not just do that with template variables?

heady valve Jan 7, 2024, 5:58 PM

#

Still trying to understand how that works. If I specify a different value in config.yml for an attribute that's in resolution_season.yml, PMM will override the value based on what I used for template_variables?

#

Example...if resolution_season.yml has vertical_offset: 10 and I add a template variable of vertical_offset: 100 to config.yml, then when PMM processes that specific library, it'll use 100 as the value, but later in the same config.yml file I could use a different vertical_offset value, in reference to the same resolution_season.yml file?

dire timber Jan 7, 2024, 6:00 PM

#

exactly

#

however you dont need to use that yml

#

- pmm: resolution
  template_variables:
    vertical_offset: 100

vague shard Jan 7, 2024, 6:01 PM

#

Yes. And it makes it 10x easier when new updates are pushed, you don’t need to really do much cause the file updates with the update.

clear jolt Jan 7, 2024, 6:02 PM

#

~~However, the default resolution overlay doesn't work at the season level. I don't know if you've made changes to attempt to add that.~~ or maybe it does. The wiki contains conflicting information.

vague shard Jan 7, 2024, 6:02 PM

#

There are so many things you can do just by using the defaults and their variables

clear jolt Jan 7, 2024, 6:04 PM

#

libraries:
  Movies:
    overlay_files:
      - pmm: resolution
  TV Shows:
    overlay_files:
      - pmm: resolution
      - pmm: resolution
        template_variables:
          builder_level: season
          vertical_offset: 100 ## push this one down a bit
      - pmm: resolution
        template_variables:
          builder_level: episode
          vertical_offset: 200 ## push this one down further

heady valve Jan 7, 2024, 6:05 PM

#

ok - let me mess around there and I'll see what I can work out

#

If I had built my own completely custom resolution file (instead of basically using the default PMM file locally) then this would all be different

#

correct?

clear jolt Jan 7, 2024, 6:07 PM

#

well, sure, since you would have created an entirely different custom file. I don't understand the question.

heady valve Jan 7, 2024, 6:07 PM

#

It's okay - typing it out made me understand.

clear jolt Jan 7, 2024, 6:11 PM

#

Your custom file appears to be well out of date compared to the current one.

heady valve Jan 7, 2024, 6:16 PM

#

clear jolt ```yaml libraries: Movies: overlay_files: - pmm: resolution TV Sho...

What's the correct indentation here if I also have a custom file path for the TV Show overlay (- file: config/episode_info3.yml )

clear jolt Jan 7, 2024, 6:39 PM

#

libraries:
  TV Shows:
    overlay_files:
      - file: /path/to/custom.yml
      - pmm: resolution
      - file: /path/to/a-different-custom.yml
      - pmm: resolution
        template_variables:
          builder_level: season
          vertical_offset: 100 ## push this one down a bit
      - file: /path/to/a-third-custom.yml
      - pmm: resolution
        template_variables:
          builder_level: episode
          vertical_offset: 200 ## push this one down further
      - file: /path/to/a-some-other-custom.yml
      - file: /path/to/the-last-custom.yml

heady valve Jan 7, 2024, 7:59 PM

#

Thanks @clear jolt @vague shard @calm kernel - it's working now. One last question is whether there's a way to have @bitter gale review my config files without creating a new support post/thread?

vague shard Jan 7, 2024, 8:06 PM

#

#bot-spam

bitter galeBOT Jan 7, 2024, 9:19 PM

#

The following was shared by @heady valve and was automatically redacted by Luma as it may have contained sensitive information.

If you feel this message should not have been redacted, resend it with !noredact in your message to avoid redaction.

#

📎 config.yml

vague shard Jan 7, 2024, 9:51 PM

#

But Luma doesn’t scan config files, but scans logs

calm kernel Jan 8, 2024, 12:03 AM

#

Luma will scan the extracted config within the log file... not just the config itself.

vague shard Jan 8, 2024, 4:55 AM

#

@heady valve if this is finished type /close

#TypeError: 'NoneType' object cannot be interpreted as an integer