You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The config.ini file used by the witness_node is parsed twice, with different parsers:
By bpo::parse_config_file to get the basic options
By boost::property_tree::ini_parser::read_ini for the logging configuration
These two parsers are not entirely compatible, which sometimes leads to the second parse failing. This results in the default logging config being used instead of that in the config file.
Specifically, the ini_parser does not support repeating options. This conflicts with the documented (in the default config file) behaviour wrt the track-account option "Account ID to track history for (may specify multiple times)".
The problem is difficult to diagnose, because the reason for the parse failure is not logged.
The text was updated successfully, but these errors were encountered:
The config.ini file used by the witness_node is parsed twice, with different parsers:
These two parsers are not entirely compatible, which sometimes leads to the second parse failing. This results in the default logging config being used instead of that in the config file.
Specifically, the ini_parser does not support repeating options. This conflicts with the documented (in the default config file) behaviour wrt the track-account option "Account ID to track history for (may specify multiple times)".
The problem is difficult to diagnose, because the reason for the parse failure is not logged.
The text was updated successfully, but these errors were encountered: