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
Download the cloud_config.yaml and the logs/wgcs_1635530341.cloud.log to a stanza instance, editing the config as needed
Run ./stanza -c cloud_config.yaml --log_file ./kv.log > kv.out (You'll want to ctrl-c) this after awhile, since it take a very long time to process fully)
Do jq . kv.log to see the error output and jq . kv.out to see what Stanza is outputting
Expected behavior
For Stanza to treat quoted fields as a single field, and not look for special characters, especially the delimiter, within them.
Environment:
Tested on both Linux and OSX
Stanza v1.2.12 and 1.2.13
Additional context
Currently affecting PoC for UPS Infosec team. This could (and likely will) be replaced for them with the XML parser (this log is all single element XML with lots of K=V pairs within the element) if/when that becomes ready. However, this is still a defect that should be remedied.
The text was updated successfully, but these errors were encountered:
Describe the bug
Parsing a key value set with
=
as delimiter will fail if the values are quoted, but contain=
character.To Reproduce
Steps to reproduce the behavior:
cloud_config.yaml
and thelogs/wgcs_1635530341.cloud.log
to a stanza instance, editing the config as needed./stanza -c cloud_config.yaml --log_file ./kv.log > kv.out
(You'll want to ctrl-c) this after awhile, since it take a very long time to process fully)jq . kv.log
to see the error output andjq . kv.out
to see what Stanza is outputtingExpected behavior
For Stanza to treat quoted fields as a single field, and not look for special characters, especially the delimiter, within them.
Environment:
Additional context
Currently affecting PoC for UPS Infosec team. This could (and likely will) be replaced for them with the XML parser (this log is all single element XML with lots of K=V pairs within the element) if/when that becomes ready. However, this is still a defect that should be remedied.
The text was updated successfully, but these errors were encountered: