The way how secondarySources are used in status-im/nimbus-eth2, they call addConfigFile again which may raise ConfigurationError. When that happened, loading the primary config file didn't result in fail, which differs in error handling from errors within itself as opposed to within secondarySources. To keep callers concise, apply same error handling behaviour regardless of whether the error occurred during primary or secondary sources processing.
etan-status
commented
1 year ago
The way how
secondarySourcesare used instatus-im/nimbus-eth2, they calladdConfigFileagain which may raiseConfigurationError. When that happened, loading the primary config file didn't result infail, which differs in error handling from errors within itself as opposed to withinsecondarySources. To keep callers concise, apply same error handling behaviour regardless of whether the error occurred during primary or secondary sources processing.