Error messages not really usable. missing line breaks about setup-go

[thboop]

Hey @TimSatke are you still encountering this issue?

If so, could you provide a link to your log or steps to reproduce?

[tsatke]

Yes I am, it is the output in the actions console. It is only commented and formatted on pull requests, not on pushes.
See e.g. failing lint jobs in tomarrell/lbadd or gojisvm/gojis

[bryanmacfarlane]

@thboop ping for follow up

[bryanmacfarlane]

@TimSatke - can you provide the block of text from your log that led to the problematic annotation? (feel free to change file names etc)

I have this PR and I would to see if it addresses your exact problem:
#48

[tsatke]

This is the text from the log. It doesn’t lead to a problematic annotation, in fact, annotations work. However, if there is no pull request, but the action runs on a normal commit, this wall of text is the only thing that can help me, and there is no annotation at all.

[bryanmacfarlane]

Thanks. So it seems like the line breaks not being honored is the root issue in this case?

The line break bytes are there and get copied if I do, but in this view, it is very hard to use.

And that leads to a wall of text. Not sure how pull request vs normal commit would influence.

I'm going to check with some runner folks.

[ericsciple]

I downloaded the logs for this job and using a hex editor it appears to be a space 0x20 not a line feed 0x0A.

I see the step uses the container action grandcolline/[email protected]. You might check with that action author whether they are capturing the output from the compiler and mutating before writing back to STDOUT.

I have never heard of the runner squashing line feeds. My best guess - if the compiler is indeed outputting line feeds? - then some other process is in the middle.

[bryanmacfarlane]

Thanks @ericsciple !

[tsatke]

Has this been resolved?