Project

General

Profile

Bug #22407

art 3.02.04 constructs modules that are not included in paths

Added by Kyle Knoepfel about 1 month ago. Updated 24 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
04/18/2019
Due date:
% Done:

100%

Estimated time:
16.00 h
Spent time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

Although the workaround includes using the --prune-config program option, this error should be fixed.

History

#1 Updated by Kyle Knoepfel about 1 month ago

  • Estimated time set to 16.00 h
  • Assignee set to Kyle Knoepfel
  • Status changed from New to Assigned
  • Category set to Infrastructure

#2 Updated by Kyle Knoepfel 29 days ago

  • % Done changed from 0 to 100
  • Status changed from Assigned to Resolved

The fix was implemented with commit art:f58a81. It involved transferring some of the information from the configuration-pruning system to the path manager. By doing this, the framework is actually more permissive about the allowed configuration. For example, the framework now allows a user to specify (e.g.)

outputs.BadModuleConfig: {}

as long as BadModuleConfig does not appear on a trigger or end path. This varies wrt. previous behavior, where a module_type parameter, at minimum, was required, even if the configuration was ignored. Additionally, any libraries corresponding to modules that are not used by the framework are no longer loaded, which also varies wrt. previous behavior.

The fix unfortunately introduces an undesirable coupling in the PathManager test between the PathManager class and the configuration-pruning facilities. This coupling should be removed, which is described in issue #22439.

#3 Updated by Kyle Knoepfel 24 days ago

  • Target version set to 3.02.05

#4 Updated by Kyle Knoepfel 24 days ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF