by Kyle Knoepfel
Attendees:
Herb Greenlee, Alex Himmel, Chris Jones, Rob Kutschke, Brian Rebel, Erica Snider
artists: Lynn Garren, Chris Green, Kyle Knoepfel, Marc Paterno
Discussion of resolved issues:
Feature #9880: Deprecate current ParameterSet::Prettifier class in favor of something easier to maintain
The current –debug-config/–config-out printout is very difficult to maintain. For the next minor release of art, the printout format will look different, but the contents will be the same.
Necessary Maintenance #9879: Introduce deprecations for ParameterSet::get_keys() and ParameterSet::get_pset_keys()
As discussed at last week’s stakeholder meeting, the aforementioned functions have been deprecated in favor of get_names() and get_pset_names(), respectively. To see the diagnostic messages emitted at compile time, see the above link.
Feature #9881: New option ALLOW_DEPRECATIONS to cetbuildtools set_compiler_flags()
An ALLOW_DEPRECATIONS option has been added to the set of allowed compiler flags. When specified along with WERROR, all uses of deprecated facilities will remain compile-time warnings and not be converted to errors.
Bug #9813: UPS_OVERRIDE
There was an expert-level request to allow use of UPS_OVERRIDE=‘-H’ option. This would enable systems to use products that don’t have matching kernel numbers.
NOvA file-level product
The NOvA file-level product will take precedence on the issues list. The artists will do an analysis to determine how much time will be required to implement the feature as requested.
Triggering SIGINT based on number of accumulated of messages
Erica had asked Chris G. earlier if it is possible to shutdown an art process after a certain number of messages of a specific type have been logged. The short answer is that the messagefacility does not provide an interface for users that would allow this behavior. Marc suggested that one can use the syslog destination, and based on the configured routing rules for logged messages, one could then trigger a shutdown that way. Erica said they will think more about the use case.