#tmdb_status filter appears to have caching issues

1 messages Β· Page 1 of 1 (latest)

remote heart
#

Setting cache: false seems to make the filter work all of the time.

Otherwise it prints out Filter Error: No TVDb ID found for Maid for every show and says Collection Warning: No items found

When it works, it prints out a couple Convert Error: No TMDb ID Found for TVDb ID: 43713 errors (3 vs hundreds of TVDB ID errors) and properly builds the collection.

Its very odd that its talking about TVDB IDs, instead of TMDB ID mapping issues (which I'd expect for a few of them).

unique warrenBOT
#

Welcome @remote heart!

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.

remote heart
unique warrenBOT
#

πŸ“ Great! Let's start to review and make recommendations... πŸ“

#

πŸ“ If you want to review this again:
: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: tecnobrat
Person who Invoked the Command: Luma
File Name: meta-no-cache.log

Table of Contents

Page 01: User Info
Page 02: PMM Info
Page 03: PMM Config.yml YAML Validation
Page 04: Plex Configuration - Section 1
Page 05: Plex Configuration - Section 2
Page 06: Plex Configuration - Section 3
Page 07: Plex Configuration - Section 4
Page 08: Plex Configuration - Section 5
Page 09: Plex Configuration - Section 6
Page 10: Plex Configuration - Section 7
Page 11: Plex Configuration - Section 8
Page 12: Rec 01 - ❌ ANIDB AUTH ERRORS
Page 13: Rec 02 - πŸ’¬ CONVERT ERROR
Page 14: Rec 03 - ⏰ PMM SCHEDULED TIME
Page 15: Rec 04 - πŸ’‘οΈPLEX DB CACHE ADVICE

#

πŸ“ Great! Let's start to review and make recommendations... πŸ“

#

πŸ“ If you want to review this again:
: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: tecnobrat
Person who Invoked the Command: Luma
File Name: meta-cache.log

Table of Contents

Page 01: User Info
Page 02: PMM Info
Page 03: PMM Config.yml YAML Validation
Page 04: Plex Configuration - Section 1
Page 05: Plex Configuration - Section 2
Page 06: Plex Configuration - Section 3
Page 07: Plex Configuration - Section 4
Page 08: Plex Configuration - Section 5
Page 09: Plex Configuration - Section 6
Page 10: Plex Configuration - Section 7
Page 11: Plex Configuration - Section 8
Page 12: Rec 01 - ❌ ANIDB AUTH ERRORS
Page 13: Rec 02 - πŸ’¬ CONVERT ERROR
Page 14: Rec 03 - ⏰ PMM SCHEDULED TIME
Page 15: Rec 04 - πŸ’‘οΈPLEX DB CACHE ADVICE

remote heart
#

Its this very simple collection that does it:

Returning Shows:            
  builder_level: show
  plex_all: true
  filters:
    tmdb_status: returning
vivid breachBOT
#
Convert Error: No TVDb ID Found for TMDb ID: 15733
Convert Error: No TMDb ID Found for IMDb ID: tt14431252

These sorts of errors indicate that the thing can't be cross-referenced between sites. For example, at the time of that error, the TMDB record for "The Two Mrs. Grenvilles" [ID 15733] didn't contain a TVDB ID. This could be because the record just hasn't been updated, or because "The Two Mrs. Grenvilles" isn't listed on TVDB.

The fix is for someone [like you, perhaps] to go to the relevant site and fill in the missing data.

remote heart
#

Yea, those aren't the issue πŸ™‚

remote heart
#

Worth mentioning, it also impacts the default status overlay, which I assume uses the same filter under the hood (I haven't checked).

The behaviour I will get with cache: true when running my overlay updates nightly, is that usually 1/2 of the time the status overlay doesn't show. My guess is that something is cached one day, and not cached the next. But it seems to work consistently when cache is set to false.

Also cache: true will work if I manually delete the cache file first. So my theory is the cache is somehow corrupt.

light idol
#

FWIW I haven’t seen this on the status overlay running it repeatedly to add overlays to new shows.

remote heart
#

With cache:true? Thats an interesting data point.

light idol
#

Yes, cache:true.

remote heart
#

How often do you run it? And curious what your cache_expiration is set to.

I am running it daily and set mine to 60.

light idol
remote heart
vivid breachBOT
#

Showing lines 2666 - 2668 of bd7bbc6ac1ed60e7f81f479c0b2ff906624d12b1/modules/builder.py ```py

2666 if item.ratingKey not in self.library.movie_rating_key_map and item.ratingKey not in self.library.show_rating_key_map:
2667 logger.warning(f"Filter Error: No {'TMDb' if self.library.is_movie else 'TVDb'} ID found for {item.title}")
2668 or_result = False

remote heart
#

Do you have only_filter_missing set to false or true?

#

I ask because that entire code block is skipped if its set to true, and mine is set to false.

light idol
#

The run today applied 129 new overlays, removed none, and showed me about a half-dozen convert errors.

#

But some new stuff got added after that, so let me run it again.

#

This run again went through fine with the same small set of convert errors as before:

|     3 | Convert Error: No TMDb ID Found for TVDb ID: 43713                                         |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 82643                                         |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 296861                                        |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 339732                                        |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 350354                                        |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 72514                                         |
|     3 | Convert Error: No TMDb ID Found for TVDb ID: 322725                                        |

113 applied this time, none removed.

remote heart
#

Interesting. I have a run going right now but I'm going to have to do some more testing tomorrow.

light idol
#

Ran again this morning with the same boring results.

remote heart
#

I blew away everything in my config dir last night (except the configs themselves) and did a full rebuild... its going now and obviously did't have a cache file to start, so its slow, haha

remote heart
unique warrenBOT
#

πŸ“ Great! Let's start to review and make recommendations... πŸ“

#

πŸ“ If you want to review this again:
: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: tecnobrat
Person who Invoked the Command: tecnobrat
File Name: meta.log

Table of Contents

Page 01: User Info
Page 02: PMM Info
Page 03: PMM Config.yml YAML Validation βœ…
Page 04: Plex Configuration - Section 1
Page 05: Plex Configuration - Section 2
Page 06: Rec 01 - ⏰ PMM SCHEDULED TIME

remote heart
#

I simplified my config so its basically the bare minimum.... and it happened.

unique warrenBOT
remote heart
#

@light idol do you have PMM_CACHE_LIBRARIES set to true?

#

Just ran it again with that explicitly set to false, but cache: true in the config, and it works.

light idol
#

I do not. PMM_CACHE_LIBRARIES apparently shows a variety of idiosyncrasies.

remote heart
#

Yea, I see some other notes in discord of folks turning that off and it fixing various issues.

#

From the docs, I'm not really clear on the benefit it gives me anyways

#

Back to my full config and see if that fixes all of my issues. I'll report back.

light idol
# remote heart From the docs, I'm not really clear on the benefit it gives me anyways

I requested it a while ago because it seemed silly to completely load the entire library multiple times per day when it wasn't changing at all. I figured PMM could read the 10000 movies the one time, then store the product of that initial read and just start there on the next run, reasoning that it was faster to reconstitute a pickled object off the disk than to ask Plex for 10000 movies again.

Apparently, though, there's some wiring under there that doesn't get connected properly when that's done.

remote heart
#

This issue appears to be gone too with that: #general-chat message

#

Ahh yea, gotcha. So load it into the SQLite DB once and then just use that from then on.

#

I'll be honest .. I think its actually running faster with that disabled.

#

Yep, working with my full config too, got past building that collection.

#

I appreciate your help -- being the "it works for me with X" was helpful πŸ™‚