You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, one of our users stumbled upon an issue where Augeas would fail to parse their configuration. I was able to narrow the exact issue down to a case that is indeed a bit strange looking.
In short: If there's a empty comment line (a whitespace character required after hash) after an If statement, Augeas fails to parse the file.
Example snippet (GitHub markdown might remove the whitespace after hash):
<If "%{HTTP_HOST} == 'example.com'">
#
Order Allow,Deny
allow from All
</If>
The text was updated successfully, but these errors were encountered:
lutter
added a commit
to lutter/augeas
that referenced
this issue
Aug 10, 2018
We used to only deal with completely empty comments after a tag opening a
section, for example '<If cond>#\n', but not with a comment that consisted
only of whitespace like '<If cond># \n'. We now accept both cases,
resulting in the same tree.
Fixeshercules-team#577
Hi, one of our users stumbled upon an issue where Augeas would fail to parse their configuration. I was able to narrow the exact issue down to a case that is indeed a bit strange looking.
In short: If there's a empty comment line (a whitespace character required after hash) after an If statement, Augeas fails to parse the file.
Example snippet (GitHub markdown might remove the whitespace after hash):
The text was updated successfully, but these errors were encountered: