Ruleset sanity silently ignores unknown range

• Rapporteur: cazfi
• Propriétaire: cazfi
• Type: Bogues
• État: Atteints
• Composant: General
• Jalon: 3.0.4 (atteints)
• Priorité: 5 - moyen
• Sévérité: 5 - moyen
• Résolution: Fixed
• Fichier: 2

Détails

req_from_str() : "If no range is given a default fallback is used rather than giving an error." The problem is; that fallback is (silently) used also when the range has been given, but it's unknown.

Ticket History (3/8 Histories)

2022-05-29 11:03 Updated by: cazfi

• New Ticket "Ruleset sanity silently ignores unknown range" created

2022-07-19 16:40 Updated by: cazfi

• Jalon Update from (Aucun) to 3.0.3 (atteints)

2022-07-29 05:49 Updated by: cazfi

• Jalon Update from 3.0.3 (atteints) to 3.0.4 (atteints)

2022-08-05 12:00 Updated by: cazfi

• File 0033-Do-not-silently-ignore-invalid-range.patch (File ID: 10007) is attached

2022-08-05 12:01 Updated by: cazfi

• Propriétaire Update from (Aucun) to cazfi
• Résolution Update from Aucun to Accepted

Commentaire

Requires that #45262 is fixed first, so that supplied rulesets won't start failing added check.

2022-08-10 10:27 Updated by: cazfi

• Résolution Update from Accepted to Aucun

Commentaire

This is a bit harsh for existing S3_0 rulesets with the hard error. Should just give a warning there.

Often falling back to the default range even results in the wanted result.

2022-08-13 18:58 Updated by: cazfi

• File 0004-Do-not-silently-ignore-invalid-range.patch (File ID: 10068) is attached

2022-08-17 00:44 Updated by: cazfi

• État Update from Ouvert to Atteints
• Résolution Update from Aucun to Fixed