Actions
Bug #17992
closedcompiler error is not helpful in certain cases
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
Compiler sometimes output parsing errors that are sometimes off.
Either the context is wrong or the error message is wrong.
The former is a complex issue to deal with but in any case adding more error checks (like in pstatement content) will end up in more precise errors.
Updated by Gaëtan POBLON over 4 years ago
- Status changed from New to In progress
Updated by Gaëtan POBLON over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Gaëtan POBLON to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder/pull/3130
Updated by Anonymous over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|f890aaf1c5d33a6b16558eb22a4321d8b4d8cfb1.
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by François ARMAND over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.2 which was released today.
Actions