#Help with imdb_search builder event.winning attribute not working as expected.

1 messages · Page 1 of 1 (latest)

patent pebble
#

I have the following 2 Oscar Best Picture collections (one for nominated and another for winning). However, both collections result in 98 items (only winning). Why is that and how can I fix the nominated collection to include all nominated movies as well and not just winning?

  Best Picture Winning - Movies:
    imdb_search:
      type: movie
      event.winning: oscar_picture
      limit: 10000
    sync_mode: sync
    smart_label: release.desc
    collection_mode: hide
    visible_library: false
    visible_home: false
    visible_shared: false
    schedule: yearly(05/02)

  Best Picture Nominated - Movies:
    imdb_search:
      type: movie
      event: oscar_picture
      limit: 10000
    sync_mode: sync
    smart_label: release.desc
    collection_mode: hide
    visible_library: false
    visible_home: false
    visible_shared: false
    schedule: yearly(05/02)
sweet blazeBOT
#

Welcome @patent pebble!

Thanks for being a Kometa Sponsor, we greatly appreciate it! Your ticket will now be diverted to <@&1097919568334311495> and <@&938443185347244033>.

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.

patent pebble
#

I am currently on: Version: 2.2.0-build2 (Docker: nightly)

devout patio
#

Can you provide a log of this happening?

#

Probably log an issue; both of those issue the same search, from which IMDB returns the same 98 items.

patent pebble
#

What would be the correct imdb_search config for the link above? I couldn't find any mention of an attribute in the wiki for groups (per the parameter in the url)

devout patio
#

What you have above would be correct so far as I know.

patent pebble
#

@modest hedge Any ideas regarding this?

modest hedge
spiral marshBOT
#
Providing TRACE or LOG REQUESTS level Log Files

We require more low-level logs from your Kometa run in order to be able to assist your further; we call these "trace logs" and they give us a more in-depth look at what is happening behind-the-scenes when Kometa is running. We may even ask for more verbose logs and those are called "log requests logs".

in order to get trace logs, you need to run Kometa again using the --trace environment variable.

in order to get log requests logs, you need to run Kometa again using the --log-requests environment variable.

Once you have completed your run with Trace or Log Requests enabled, you can find your meta.log file within the logs folder of your Kometa config folder [typically where you would find your config.yml]

We suggest you quickly review any log file created using --log-requests as they may contain API keys or other sensitive data.

Drag-and-drop your meta.log file directly into the Discord support thread. If the file is larger than 50mb, we suggest zipping it or uploading it to another file-sharing website.

Please DO NOT manually extract, copy and paste text from your log files directly into Discord as the formatting can be difficult to read and can often redact parts of the log file that are important for full context.

patent pebble
#

No problem I will post trace logs but it may take 1.5 weeks because my little nieces are visiting and keeping me away from the PC!

devout patio
#

I can repro this so will generate a log.

devout patio
sweet blazeBOT
#

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

devout patio
modest hedge
#

@devout patio so this may feel random but if you flip the two collections so nominated runs first is it magically fixed?

devout patio
#

running...

#
|              Title              |   +   |   =   |   -   | Run Time | Status                        |
|=================================|=======|=======|=======|==========|===============================|
| Best Picture Nominated - Movies |    39 |    19 |     0 |  0:01:44 | Created and Updated Metadata  |
| Best Picture Winning - Movies   |     0 |    19 |     0 |  0:00:04 | Created and Updated Metadata  |
#
[INFO]     | Processing IMDb Search:
[INFO]     |     limit: 10000
[INFO]     |     type: ['movie']
[INFO]     |     event: ['oscar_picture']
[TRACE]    | {'locale': 'en-US', 'first': 250, 'titleTypeConstraint': {'anyTitleTypeIds': ['movie']}, 'sortBy': 'POPULARITY', 'sortOrder': 'ASC', 'awardConstraint': {'allEventNominations': [{'eventId': 'ev0000003', 'searchAwardCategoryId': 'bestPicture'}]}}
[DEBUG]    | https://raw.githubusercontent.com:443 "GET /Kometa-Team/IMDb-Hash/master/HASH HTTP/1.1" 200 72
[DEBUG]    | Starting new HTTPS connection (1): api.graphql.imdb.com:443
[DEBUG]    | https://api.graphql.imdb.com:443 "POST / HTTP/1.1" 200 62583
[DEBUG]    | https://api.graphql.imdb.com:443 "POST / HTTP/1.1" 200 60151
[DEBUG]    | https://api.graphql.imdb.com:443 "POST / HTTP/1.1" 200 27500
[DEBUG]    |
[DEBUG]    | 614 IDs Found

and

[INFO]     | Processing IMDb Search:
[INFO]     |     limit: 10000
[INFO]     |     type: ['movie']
[INFO]     |     event.winning: ['oscar_picture']
[TRACE]    | {'locale': 'en-US', 'first': 250, 'titleTypeConstraint': {'anyTitleTypeIds': ['movie']}, 'sortBy': 'POPULARITY', 'sortOrder': 'ASC', 'awardConstraint': {'allEventNominations': [{'eventId': 'ev0000003', 'searchAwardCategoryId': 'bestPicture', 'winnerFilter': 'WINNER_ONLY'}]}}
[DEBUG]    | https://api.graphql.imdb.com:443 "POST / HTTP/1.1" 200 26468
[DEBUG]    |
[DEBUG]    | 98 IDs Found

Looks like changing the order did the right thing

modest hedge
#

yea its editing an in place dict i just need it to copy it instead ill push a fix for nightly

#

this should fix it for either way

devout patio
#

@patent pebble ^^ workaround and fix

spiral marshBOT
#

chazlarson used !aenh

@patent pebble, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.

patent pebble
#

Thank you so much Sohjiro for the quick fix and workaround and Chaz for helping to reproduce and send logs while I'm away from the PC, much appreciated! I will test this out once I'm back but trust that all is working so we can close this out and I'll reopen it if I notice any issues 🙂