Project

General

Profile

Actions

Feature #1842

closed

Improve error reporting of invalid reqs in rulesets

Added by Dean Brown 6 days ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Server
Target version:
-
Start date:
12/26/2025
Due date:
% Done:

0%

Estimated time:

Description

When loading a ruleset finds an invalid req it calls ruleset_error() and shows an error message -

"has invalid or unknown req: [type] [name]"

When the problem is an invalid range, this is not as useful as it could be. If debug level is ERROR then a better detailed message is shown, but that's not the default setting.


Files

1842_Main.patch (6.33 KB) 1842_Main.patch Dean Brown, 12/26/2025 06:19 AM
1842_S3_3.patch (6.35 KB) 1842_S3_3.patch Dean Brown, 12/26/2025 06:19 AM
1842_S3_2.patch (6.32 KB) 1842_S3_2.patch Dean Brown, 12/26/2025 06:20 AM

Updated by Dean Brown 5 days ago

Actions #2

Updated by Dean Brown 5 days ago

  • File deleted (1842.patch)
Actions #3

Updated by Dean Brown 5 days ago

Actions #4

Updated by Marko Lindqvist 5 days ago

Dean Brown wrote:

If debug level is ERROR then a better detailed message is shown, but that's not the default setting.

Umh, ERROR is such a high level that those messages are shown almost always (only if the debug level would be FATAL, they would not)

Actions #5

Updated by Dean Brown 5 days ago

  • Status changed from New to Closed

My bad - I must have noticed only the last error message and missed that you get 2 error messages. Closing this as invalid.

Actions

Also available in: Atom PDF