Bug #7622
closed
Technique files contains UTF-8 chars (especially spaces)
Added by François ARMAND almost 9 years ago.
Updated over 7 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Infrequent - complex configurations | third party integrations
Description
There is several techniques files containing UTF-8 chars, especially an UTF-8 space.
AFAIK, these chars are only in comments, but I only looked in system techniques.
The problem with a change to remove them will be in merge where it will be hard to know what is the correct space to get.
For information, the joined file is a list of such chars in system techniques.
Files
- Assignee set to François ARMAND
I understand the observation, but I don't understand the problem - you have filed this as a bug, so could you please explain the negative impact or perceived risk?
- Target version set to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
We had a problem with a cfengine command not doing what was expected due to a utf-8 space in place of a space.
We also add a problem with a third party scripts (python I believe?) that didn't parsed the content as expected due to them (it was breaking regex).
The bigger problem is that it breaks any regex apply on these file when done by human looking for space. It's surprising and deceving.
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Target version changed from 3.1.19 to 3.1.20
- Priority set to 0
- Status changed from Discussion to New
- Assignee deleted (
François ARMAND)
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
I will add a test to 'make test' to detect any such characters, at the same time as removing all existing ones. This should enable easy detection if they were to come back, or a merge were to reintroduce them.
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1139
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by