Failed to parse config

[Corginyan]

Found a small bug. There is an error parsing such constructs, but only if the comment contains parentheses with spaces inside them. Without spaces, everything is processed normally.

log_format analytics escape=json '{'
	'"request_length": "$request_length"' # text (spaces inside) text
'}';

[davispuh]

I don't think this is only way it fails.
I just tried it on my nginx and it doesn't work :)

$ nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

$ gixy
[nginx_parser]  ERROR   Failed to parse config "/etc/nginx/nginx.conf": char 12 (line:1, col:13)

==================== Results ===================
No issues found.

==================== Summary ===================
Total issues:
    Unspecified: 0
    Low: 0
    Medium: 0
    High: 0

It's very bad that it says No issues found when fails to even parse which is incredibly wrong for a validator tool.

Also it even displays wrong line where the issue is, see line:1 which is empty in my case :D

My nginx config is very big and complicated so it seems like tons of work to find where exactly it fails so first thing that should be fixed would be to show correct line where the failure is.

[davispuh]

Ohh turns out my issue was #122 and I had pyparsing 3.1
Looks like there's a lot of open issues due to this #138 #131 #124