search

spacepy / dbprocessing

Automated processing controller for heliophysics data
5 stars 4 forks source link

DBRunner doesn't seem to require all required inputs #75

Open jtniehof opened 3 years ago

jtniehof commented 3 years ago

When using DBRunner and the -u argument, if there are multiple required inputs, it looks like the file is run if only some are present. This may be related to #74 .

Minimal example to reproduce issue:

Using DBRunner.py -m ~/dbp_codes/tmp.sqlite -s 20210317 -u -n 1 5, a file gets called with only one of the required inputs.

OS, Python version, and dependency version information:

Linux-4.4.0-201-generic-x86_64-with-Ubuntu-16.04-xenial
sys.version_info(major=2, minor=7, micro=12, releaselevel='final', serial=0)
sqlalchemy=1.0.11

Version of dbprocessing

git master (142a4976f66d28d227e95ae6acfc73376adc660f)

Closure condition

This is probably going to require #74 to be fixed first, as it's probably relevant to the distinction between able-to-run and able-to-be-updated. Need to have a test of DBRunner that has a product with two required inputs, only one is present (and thus not the output), and it should not run, with or without -u.