Binary output breaks log display "Error fetching logs for task"

When a task sends arbitrary bytes to stderr or stdout, the log display fails completely with the message "Error fetching logs for task". Examples: https://builds.sr.ht/~andres/job/49896 https://builds.sr.ht/~andres/job/49897

Assigned to
3 years ago
2 years ago
No labels applied.

~sircmpwn 3 years ago

What do you think would be the correct behavior here?

~andres 3 years ago

In my case, the binary output was unintentional. So I would have been just fine an error message telling me that the reason I cannot see the log is that the task produced output that wasn't valid UTF-8 (or whatever the encoding of the day is). It wold be nice to be able to see the good parts of the log even if there is some garbage in there, but I am not sure what an appropriate granularity would be or how it could be implemented (though terminal emulators do various levels of okay at this).

~krathalan closed duplicate ticket #294 2 years ago

~macbook 2 years ago

Hi everyone.

I'm also affected by this issue, and what's really problematic is that if affects all tasks in a build: https://builds.sr.ht/~macbook/job/271790

Register here or Log in to comment, or comment via email.