No verbose matching output when no element matches
Bug #1834302 reported by
Max Landauer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| logdata-anomaly-miner - lightweight tool for log checking, log analysis |
Fix Released
|
Medium
|
Markus Wurzenberger | ||
Bug Description
The DebugMatchContext is expected to print the shortest unmatched data for unparsed log atoms. Usually, this is the remaining line starting from the last unmatched element.
However, when not a single element matches, the output is None. This is because the update method in the class DebugMatchContext is never called, leaving shortestUnmatch
Revision history for this message
| Markus Wurzenberger (mwurzenberger) wrote | #1 |
| Changed in logdata-anomaly-miner: | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
| assignee: | nobody → Markus Wurzenberger (mwurzenberger) |
To post a comment you must log in.
Fixed bug by initializing shortestUnmatch