00:33 <gallo[m]> Hmm, this update still needs to be upstreamed. The maintainers are not so much concerned with this issue. I suppose that the majority of the LAVA users only use it to make simpler tests and does not require the level of attention of transparent logs like us.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/EPrMJrLyLMZMQotfZURHdjMr>)

00:34 <gallo[m]> damn (matrix has summarized my message, resending)

00:34 <gallo[m]> Hmm, this update still needs to be upstreamed

00:34 <gallo[m]> The maintainers are not so much concerned with this issue. I suppose that the majority of the LAVA users only use it to make simpler tests and does not require the level of attention of transparent logs like us.

00:34 <gallo[m]> You would need to patch it manually as a hotfix and reinstall at least the lava_dispatcher/shell.py script.

00:34 <gallo[m]> I can delegate this burden to the Mesa CI job submitter script if you think this procedure is not worth it. Still, it will make the submitter hackier as it already is and prone to eventual new fancy logs that use another sequence of special characters.

00:35 <gallo[m]> fwiw, this is the related LAVA upstream issue: https://git.lavasoftware.org/lava/lava/-/issues/561

12:20 <enunes> gallo[m]: I can make it a local fix but I would be more comfortable making it knowing that next time I update it wont be overridden

15:33 <gallo[m]> enunes: That is totally fair. I am asking the commit author if he could retry to push the fix upstream. I hope this fix will be embedded in your next LAVA update.