Steps to reproduce
- Open the System logs page
- Set Start date to today and Start time to a few minutes ago (the default is yesterday at midnight, which hides the problem — see Actual behavior)
- Enable the Regular expression toggle
- Type an invalid pattern in Search query, for example
GET(
- Click Follow logs
Expected behavior
The page reports that the search pattern is invalid and leaves the follow state.
Actual behavior
Nothing happens: no log lines, no error notification, and the page stays in the follow state indefinitely. Only Stop following ends it. An invalid pattern is indistinguishable from a valid search that has not matched anything yet, so the user has no way to tell the search is broken.
The failure is reported only when the selected start time is old enough. With the default start period — yesterday at midnight — the same invalid pattern does produce an error, which is why the problem is not evident unless the period is narrowed to a recent time.
Components
ns8-core 3.22 and later
See also
Steps to reproduce
GET(Expected behavior
The page reports that the search pattern is invalid and leaves the follow state.
Actual behavior
Nothing happens: no log lines, no error notification, and the page stays in the follow state indefinitely. Only Stop following ends it. An invalid pattern is indistinguishable from a valid search that has not matched anything yet, so the user has no way to tell the search is broken.
The failure is reported only when the selected start time is old enough. With the default start period — yesterday at midnight — the same invalid pattern does produce an error, which is why the problem is not evident unless the period is narrowed to a recent time.
Components
ns8-core 3.22 and later
See also