--output allowed to be an empty string

[ijiraq]

I ran a batch of processing and set --output " (i.e., the empty string). This placed the output in a TIME based run collection in my butler directory. Shouldn't passing an empty string as --output raise an error?

e.g. pipetask run -b BUTLER -p pipeline.yaml -i u/me/in --ouput ""

output of pipeline.yaml is now in BUTLER/20241120T023747Z

This sort of works but, rerunning with --skip-existing-in "" doesn't make pipetask very happy. The butler lists "" as a CHAINED collection and has no trouble, but something in the skip logic fails.

Empty string as an allowed value for --output feels wrong.

[timj]

Thanks. I think you are the first person to notice this. It's not intentional.

I've made a Jira ticket for this at DM-47726.