Clunky handling of walking a workflow with no input files

[GoogleCodeExporter]

Presently, if a step in the workflow produces no output files that match the 
input files of another workflow, an assertion is raised from within the walker 
running under celery:

Traceback (most recent call last):   File 
"/usr/local/python/ccgapps/yabiadmin/release/yabiadmin/yabiengine/enginemodels.p
y", line 346, in create_tasks     self._create_tasks(tasks)   
File 
"/usr/local/python/ccgapps/yabiadmin/release/yabiadmin/yabiengine/enginemodels.p
y", line 404, in _create_tasks     task.add_task(*(task_data+[name]))   
File 
"/usr/local/python/ccgapps/yabiadmin/release/yabiadmin/yabiengine/enginemodels.p
y", line 478, in add_task     self.command = template.render()   
File 
"/usr/local/python/ccgapps/yabiadmin/release/yabiadmin/yabiengine/commandlinetem
plate.py", line 405, in render     assert len(batchfiles), "batch_files passed 
in has %d entries which is not enough for command tempate 
%r"%(len(self.batchfiles),self) AssertionError: batch_files passed in has 0 
entries which is not enough for command tempate 
<yabiadmin.yabiengine.commandlinetemplate.CommandTemplate object 
Exception raised in workflow::walk

This needs to be handled gracefully within a normal operation of the code (ie. 
it is not an 'exceptional' cirsumstance and thus shouldnt raise an exception)

Original issue reported on code.google.com by retrogra...@gmail.com on 12 Jan 2012 at 3:27

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:51

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:51

• Changed state: New