[Tool #124] Local Log Parser level filters become inconsistent with the displayed rows and count

[baixiangcpp]

Summary

Local Log Parser shows inconsistent state after changing level filters. A WARN row disappears, but the Filtered count remains at 5 and the checkbox state does not match the rows currently displayed.

Affected tool: Local Log Parser
Route: https://byteflow.tools/en/local-log-parser
Observed during browser acceptance: 2026-08-18

Reproduction

1. Open the affected route.
2. Click Try Example.
3. Click Parse Logs and confirm the example contains 5 parsed rows, including at least one WARN row.
4. Change the level checkboxes so WARN is excluded.
5. Inspect the visible rows, Filtered count, and checkbox state.
6. Re-parse the same input.

Actual output

After the level-filter operation:

• the WARN row disappears from the table;
• Filtered still reports 5;
• the level checkboxes do not match the levels represented by the table;
• re-parsing does not reliably restore a consistent filter/result state.

Keyword filtering, JSON Lines parsing, and CSV/JSON export otherwise work.

Expected output

The table, selected level filters, and Filtered count must be derived from the same current filter state. If WARN is excluded, WARN rows must be hidden and Filtered must decrease to the actual number of visible rows. Re-parsing should reset or preserve filters deterministically and keep the count synchronized.

Impact

Users cannot trust the displayed count or know which log levels are included, which undermines filtering and export decisions.

Regression coverage

Test every combination of INFO, WARN, and ERROR filters, then combine level and keyword filters. Assert that checkbox state, visible rows, Filtered count, and exported data all agree.