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
Since #250, I have an issue with the _classify_pandoc_logging function : when the parsed message does not fit the expected format, the parsing can end in a KeyError. For example, pandoc-include has a warning formatted like this:
[Warn] included file not found: path_of_the_file
Warn isn't in the dictionnary of expected log levels, which raises a KeyError on line 422:
yieldlevel_map[level], "\n".join(log_msgs)
The text was updated successfully, but these errors were encountered:
I'm not very familiar with this codebase, but I'd say both solutions can be implemented: a classification that tries to include all the message types you're aware of, with an additional fallback case to handle new cases. In the fallback, I'd say that re-logging the messages as "warning" would be best.
Added logic for if classify_pandoc_logging can't identify the correct logging level (#271)
* Added test logic for invalid log levels
* Now falling back to default log level, if classify can't identify the correct level
Since #250, I have an issue with the _classify_pandoc_logging function : when the parsed message does not fit the expected format, the parsing can end in a KeyError. For example, pandoc-include has a warning formatted like this:
[Warn] included file not found: path_of_the_file
Warn
isn't in the dictionnary of expected log levels, which raises a KeyError on line 422:The text was updated successfully, but these errors were encountered: