<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">This does not make much sense to me as it sounds as: Lets convert all the images to B&W because it takes less space on disk and tell user to use JS based AI to recolor to them. </div><div class=""><br class=""></div><div class=""><div class="">Displaying ANSI does not mean colorize my logs, has nothing to do with it.</div><div class=""><br class=""></div><div class="">Displaying ANSI is about respecting the output produced by the executed tools.</div><div class=""><br class=""></div><div class="">Zuul should respect the output received on stderr/stdout and display it like a console/ terminal. If the job author decides to use ANSI or not is up to them. </div><div class=""><br class=""></div><div class="">Still, Zuul itself as product should just render ANSI content, mainly because I do not see any use-case where someone would want to render that text as RAW, as we all know ANSI escapes do not add any value to the user.</div><div class=""><br class=""></div><div class="">Still, if the ability to display raw text, without ansi conversion is a real need, I could spend few more hours to implement it and add a preference option. Still, think twice before asking for a feature that adds some code complexity and may not prove to be of real practical use. We all know that the raw text is still available inside the big json file in case someone has doubs regarding what was rendered may be wrong.</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 27 Aug 2020, at 17:24, Sean Mooney <<a href="mailto:smooney@redhat.com" class="">smooney@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">On Thu, 2020-08-27 at 08:37 -0700, Clark Boylan wrote:</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">On Thu, Aug 27, 2020, at 1:11 AM, Sorin Sbarnea wrote:<br class=""><blockquote type="cite" class="">At this moment Zuul web interfaces displays output of commands as raw,<span class="Apple-converted-space"> </span><br class="">so any ANSI terminal output will display ugly artifacts.<br class=""><br class="">I tried enabling ANSI about half a year ago but even after providing<span class="Apple-converted-space"> </span><br class="">two different implementations, I was not able to popularize it enough.<br class=""><br class=""><br class="">As this is a UX related feature, I think would like more appropriate to<span class="Apple-converted-space"> </span><br class="">ask for feedback from openstack-discuss, likely the biggest consumer of<span class="Apple-converted-space"> </span><br class="">zuul web interface.<span class="Apple-converted-space"> </span><br class=""><br class="">Please comment/+/- on review below even if you are not a zuul core. At<span class="Apple-converted-space"> </span><br class="">least it should show if this is a desired feature to have or not:<br class=""></blockquote><br class="">Without my Zuul hat on but with my "I debug a lot of openstack jobs" hat I would prefer we remove ansi color controls<br class="">from our log files entirely. They make using grep and other machine processing tools more difficult. I find the<br class="">utility of grep, ^F, elasticsearch, and the log level severity filtering far more useful than scrolling and looking<br class="">for colors that may be arbitrarily applied by the source.<br class=""></blockquote><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">if we can remove them form the logs but use a javascpit lib in the viewer to still highlight thing that might be the</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">best of both worlds</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">i do fine the syntax hyilighign nice but we dont need color codes to do that.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""><blockquote type="cite" class=""><br class=""><a href="https://review.opendev.org/#/c/739444/" class="">https://review.opendev.org/#/c/739444/</a><span class="Apple-converted-space"> </span>✅<br class=""><br class="">This review also includes a screenshot that shows how the rendering<span class="Apple-converted-space"> </span><br class="">looks (an alternative for using the sitepreview)<br class=""><br class="">Thanks<br class="">Sorin Sbarnea</blockquote></blockquote></div></blockquote></div><br class=""></div></div></body></html>