Open stirlingalgermissen opened 3 years ago
@stirlingalgermissen are you piping this output to a file? or running with the output file flag? If the former, I think the latter make fix this? If not, this is a bug we will look into.
-r,--report-file <file name> Specify the report file name. Default
is standard out.
Yes writing the report to a file works. This issue is specific to when the report is written to stdout
@stirlingalgermissen copy that. i'm not sure this is something we are going to be able to fix, unfortunately. those dots to stdout are actually intentional for long-running validations to show a status to the user that validate hasn't frozen on them. i will keep this on the backburner in case we (or someone) comes up with a better idea on how to do this.
This breaks APPS processing for M20. Is it not possible to create valid json with stdout?
@stirlingalgermissen sorry for the delay here. we will update the code to not output the status information when the report output == JSON, however, we recommend using the JSON report output as a workaround for the foreseeable future.
Thanks - yeah that's our plan for resolving this on our end
π Describe the bug
VTool creates invalid JSON when processing M20 mesh files.
π To Reproduce
Steps to reproduce the behavior: Run VTool on the attached example dataset. Command is:
Config is:
Output is:
Note the periods in the JSON output
π΅οΈ Expected behavior
VTool returns a report with valid JSON
π Version of Software Used
π©Ί Test Data / Additional context
NLF_0009_0667756282M606RAS_N0030000NCAM05000_0A0295J03.zip
π₯ System Info
π¦ Related requirements
βοΈ Engineering Details