Open unkarjedy opened 2 years ago
https://www.wikiwand.com/en/ANSI_escape_code
Example of logs:
[22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0m [34mTest run [0morg.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m [34m started [0m [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mtest moduleDescriptionForTarget succeeds for build targets with Scala [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mtest createScalaModuleDescription [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mtestGetScalaSdkData [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mtest mergeModules [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mcalculateModuleDescriptions succeeds for build targets with Scala [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0mTest org.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m. [36mtest projectNode [0m ignored [0m [22:03:13] : [Step 2/2] [0m[ [0m [0minfo [0m] [0m [0m [34mTest run [0morg.jetbrains.bsp.project.importing. [33mBspResolverLogicProperties [0m [34m finished: [0m [34m0 failed [0m [34m, [0m [33m6 ignored [0m [34m, 0 total, 0.036s [0m [0m
How Team City renders it:
How Log Analyzer renders it:
If there is no fast way to support ASCII sequences then at least there could be an option to filter out all ASCII sequences from the logs to at least view the text conveniently.
Bit of a plug here but I have a library that may help: https://github.com/leaanthony/go-ansi-parser
https://www.wikiwand.com/en/ANSI_escape_code
Example of logs:
How Team City renders it:
How Log Analyzer renders it:
If there is no fast way to support ASCII sequences then at least there could be an option to filter out all ASCII sequences from the logs to at least view the text conveniently.