apero_processing asks for user input when no files are present even when TRIGGER_RUN is true

[cusher]

On branch: v0.7.289-stable-test

Documentation seems to indicate that setting TRIGGER_RUN true, or passing in trigger=True should prevent this, but that doesn't seem to be the case.

Able to work around it for now by modifying drs_processing.py, where I changed the following:

         # deal with empty database (after conditions)
        if idb_len == 0:

to

         # deal with empty database (after conditions)
         if idb_len == 0 and 'TRIGGER_RUN' not in params:

[njcuk9999]

its probably not worth continuing if the database is empty.

What would the best response be?

I guess the prompt is a problem so we can not have the user prompt, but maybe keep the exception to be caught higher up?
Or would you rather the code just stopping there without an exception?

[cusher]

The way I currently have things set up, it doesn't matter too much one way or the other. The main thing is have it able to run non-interactively i.e. so it won't hang when there is no user input.

But in terms of what makes most sense, I could see considering it a "normal use case" for the trigger mode to run on an empty directory e.g. if you are running it on a specific night directory before files have started coming in for that night. So if you consider that case valid/supported, it probably shouldn't throw an exception there would be my thought.