You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2022. It is now read-only.
In current design the standard output/error stream is taken as the main outputs of a job. But it can be totally messes. And the exit code dis also included in it with a header of [exitcode]. Things are even worse when you have some outputs unmuted like curl. These kind of commands will output a lot of segments of format characters to form a better looking in terminals.
So it's necessary to define a new stream or format in current streams which is the output of job, maybe a one line string in JSON, eg. .
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In current design the standard output/error stream is taken as the main outputs of a job. But it can be totally messes. And the exit code dis also included in it with a header of
[exitcode]
. Things are even worse when you have some outputs unmuted like curl. These kind of commands will output a lot of segments of format characters to form a better looking in terminals.So it's necessary to define a new stream or format in current streams which is the output of job, maybe a one line string in JSON, eg. .
The text was updated successfully, but these errors were encountered: