Project

General

Profile

Bug #20692

fife_launch requires all config sections, event if empty

Added by Kevin Retzke 9 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
08/28/2018
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Trying to run the simple example given the following error:

after includes:  [('group', 'fermilab'), ('wrapper', 'file:///${FIFE_UTILS_DIR}/libexec/fife_wrap')]
Traceback (most recent call last):
  File "/grid/fermiapp/products/common/db/../prd/fife_utils/v3_1_3/NULL/bin/fife_launch", line 237, in <module>
[global]
    l.launch(options.dry_run)
  File "/grid/fermiapp/products/common/db/../prd/fife_utils/v3_1_3/NULL/bin/fife_launch", line 56, in launch
    cmd = self.build_launch()
  File "/grid/fermiapp/products/common/db/../prd/fife_utils/v3_1_3/NULL/bin/fife_launch", line 142, in build_launch
    for k,v in self.cfg.items("job_setup", raw=1):
  File "/usr/lib64/python2.6/ConfigParser.py", line 589, in items
    raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'job_setup'

So it seems that all config sections need to be present. Suggest either add the following three lines to the example:

[job_setup]
[job_output]
[sam_consumer]

or setting defaults for those sections and/or handling the NoSectionError.

Associated revisions

Revision 23c22c4f (diff)
Added by Marc Mengel 8 months ago

patch for issue #20692

History

#1 Updated by Marc Mengel 9 months ago

Updated the documentation for now; I'm going to look at toning down the checks in the code...

#2 Updated by Marc Mengel 8 months ago

  • Status changed from New to Closed
  • Target version set to v3_2_4

Wrapped cfg.items with a cfg_items which just returns an empty list if the section isn't there. Then checked explicitly for [global] [submit] and [executable] which ought to be the minumum set.



Also available in: Atom PDF