(Auto)fallback to ANSI-less output in CI #147
Comments
|
Yeah, that is to be expected. The purpose of nom is to print a live status report below the log. I am not aware that this is possible in something like gitlab ci. (because there are afaict no control codes available to remove previous lines.) Am I wrong in thinking this is not possible or do you have some other ideas how nom should behave? |
|
If anyone has a good suggestion what to do here, please share. Until then I am closing this as not planned. |
|
Dumping notes here just in case: Using ncurses it seems there is a way to write to the terminal (using newterm) without scrambling stdout. Maybe that would work well enough in cases where ther is no terminal per se. See https://stackoverflow.com/questions/8371877/ncurses-and-linux-pipeline and https://stackoverflow.com/questions/53696818/how-to-i-make-python-curses-application-pipeline-friendly. A bit of work to move to a proper ncurses since nom is ANSII escapes based. |
|
I still don't understand why we would do that. I see no point in using nom in a CI pipeline. |
|
That is a perfectly valid and understandable point. Alas, we are using nom as part of our direnv setup to help developers understand what they are waiting for. Thanks for the project by the way, it is really useful and has a very understandable display.
My point is that I prefer not to special-case CI wrt. dev workflows. Because then it gets trivial to have a green ci where nom is broken go unnoticed until deployed.
Maybe having a flag that makes nom transparent (think `id`) ?
Not sure it has to be implemented in nom. Could be a patch or something. I see this thread as a way to share ideas with ppl with the same concerns.
Le 26 janvier 2025 11:54:40 GMT+01:00, maralorn ***@***.***> a écrit :
…I still don't understand why we would do that. I see no point in using nom in a CI pipeline.
--
Reply to this email directly or view it on GitHub:
#147 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
|
Aaah, that makes sense. |
maralorn
changed the title
I'm trying to integrate this into my CI pipeline on gitlab and am getting output like the following:
I tried setting
TERMas in https://docs.gitlab.com/ee/ci/yaml/script.html#job-log-output-is-not-formatted-as-expected-or-contains-unexpected-characters but it doesn't seem to make a difference.The text was updated successfully, but these errors were encountered: