Project

General

Profile

Feature #11410

Implement configuration validation for messagefacility

Added by Kyle Knoepfel over 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
01/13/2016
Due date:
% Done:

100%

Estimated time:
Spent time:
Duration:

Description

Due to poor documentation and the perhaps obscure behavior of logging messages, we should implement configuration validation/description for messagefacility including:

  • validation for supported destinations (e.g. cerr)
  • validation for general messagefacility configurations (e.g. debugModules)

Doing so will require moving where some of the configuration-loading is done--viz., moving parameter retrievals from MessageLoggerScribe to the dedicated destination plugins.

History

#1 Updated by Kyle Knoepfel over 4 years ago

  • Status changed from New to Accepted

#2 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from Accepted to Assigned
  • Assignee set to Kyle Knoepfel
  • % Done changed from 0 to 70

#3 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from Assigned to Resolved
  • Target version set to 2.08.00
  • % Done changed from 70 to 100

Implemented with many commits, the last of which is messagefacility:bc58e88.

Also associated with this are the changes that were necessary in other packages to accommodate this, including:

  • migrating code from art to cetlib and fhicl-cpp,
  • implementing improvements to art --print-description to allow disambiguation between (e.g.) file_mfPlugin and file_mfStatsPlugin

#4 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF