Regexp plugin runs during input phase

[FallingReign]

I have noticed that the regexp plugin is firing off during input when it should be during filter with a priority of 172 as per the flexget plugins output.

I am using regexp in the following manner...

    regexp:
      reject:
        - reality: {from: trakt_genres}

Can someone validate?

[gazpachoking]

What sort of info is leading you to believe it's running early?

[FallingReign]

Here is an example config I just quickly put together. (Some additional genre filters removed.)

tasks:
  test-task:
    manual: yes
    trakt_lookup: yes
    trakt_list:
      account: my-trakt-account
      list: trending
      type: shows
    if:
      - (now|formatdate('%Y')|int - title|re_replace('^.*\((\d{4})\).*$','\`')|int ) > 0: reject
    regexp:
      reject:
        - reality: {from: trakt_genres}
    exec:
      on_start:
        phase: echo "on_start..."
      on_input:
        phase: echo "on_input..."
      on_filter:
        phase: echo "on_filter..."
      on_output:
        phase: echo "on_output..."
      on_exit:
        phase: echo "on_exit..."

The expected order of operations would be that the if statement is able to reject entries before the regexp during the input phase.
That being said, the debug output shows this (truncated):

2019-05-30 18:36 INFO     manager                       Test database created
2019-05-30 18:36 VERBOSE  task_queue                    There are 1 tasks to execute. Shutdown will commence when they have completed.
2019-05-30 18:36 VERBOSE  trakt_list    test-task        Retrieving `shows` list `trending`
2019-05-30 18:36 INFO     exec          test-task        Would execute: echo "on_start..."
2019-05-30 18:36 INFO     exec          test-task        Would execute: echo "on_input..."
2019-05-30 18:36 VERBOSE  details       test-task        Produced 610 entries.
2019-05-30 18:37 VERBOSE  task          test-task        REJECTED: `iZombie (2015) S01E01` by regexp plugin because regexp 'Crime' matched field 'trakt_genres'
2019-05-30 19:13 VERBOSE  task          test-task        REJECTED: ...
2019-05-30 19:13 VERBOSE  task          test-task        REJECTED: `24 Hours in A&E (2011) S01E01` by regexp plugin because regexp 'Documentary' matched field 'trakt_genres'
2019-05-30 19:13 VERBOSE  task          test-task        ACCEPTED: `iCarly (2007) S01E01` by series plugin because choosing first acceptable match
2019-05-30 19:13 VERBOSE  task          test-task        ACCEPTED: ...
2019-05-30 19:13 VERBOSE  task          test-task        ACCEPTED: `11.22.63 (2016) S01E01` by series plugin because choosing first acceptable match
2019-05-30 19:13 VERBOSE  task          test-task        REJECTED: `iCarly (2007) S01E01` by if plugin because matched requirement: (now|formatdate('%Y')|int - title|re_replace('^.*\((\d{4})\).*$','\`')|int ) > 0
2019-05-30 19:13 VERBOSE  task          test-task        REJECTED: ...
2019-05-30 19:13 VERBOSE  task          test-task        REJECTED: `11.22.63 (2016) S01E01` by if plugin because matched requirement: (now|formatdate('%Y')|int - title|re_replace('^.*\((\d{4})\).*$','\`')|int ) > 0
2019-05-30 19:13 INFO     exec          test-task        Would execute: echo "on_filter..."
2019-05-30 19:13 VERBOSE  details       test-task        Summary - Accepted: 24 (Rejected: 586 Undecided: 0 Failed: 0)
2019-05-30 19:13 INFO     exec          test-task        Would execute: echo "on_output..."
2019-05-30 19:13 INFO     exec          test-task        Would execute: echo "on_exit..."

[FallingReign]

Actually on further inspection I think the confusion here is that I was expecting the if plugin to be able to run during the start phase after it received the entries from the trakt_lookup; though it seems that the if plugin runs in the filter phase. Which raises another question, why is the if being pushed back to the filter phase? (or does it execute on every phase?

To resolve the issue in the op I'm sure using plugin_priority to bump the if plugin up above the regexp plugin would have the desired effect - reduce calls to the trakt api.

[gazpachoking]

I think you've figured it out. if plugin does indeed run on filter phase when accepting/rejecting entries. We can't really predict which plugins are going to be more expensive so it's hard for the built in priority to be optimized for every use (for example, you could use the trakt_ fields in if plugin, and then be using regexp on the title, and prefer the reverse order.) Using plugin_priority is the right answer to move its priority around if you want to optimize that sort of thing.