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
Some commands use a return character at the end of each line in order to overwrite the previous output line with new data. This is often used to show progress of the running command. An example is the dc3dd command. This command outputs the progress of the command to one line that consistently gets overwritten with the new progress stats. If a long running command does this the output will continually be saved to the buffer and not passed to the go channel in the Write function of OutputStream because this function only checks for \n or \r\n at the end of a line. Because a command like this will never have a \n at the end of an output line the buffer will overflow every time the command is run.
The text was updated successfully, but these errors were encountered:
I met with the problem same as you. This repo may be helpful.
I change the delimiter to \n or \r.
Ignore \r\n Because \r\n only useful in Windows environment.
Some commands use a return character at the end of each line in order to overwrite the previous output line with new data. This is often used to show progress of the running command. An example is the
dc3dd
command. This command outputs the progress of the command to one line that consistently gets overwritten with the new progress stats. If a long running command does this the output will continually be saved to the buffer and not passed to the go channel in theWrite
function ofOutputStream
because this function only checks for\n
or\r\n
at the end of a line. Because a command like this will never have a\n
at the end of an output line the buffer will overflow every time the command is run.The text was updated successfully, but these errors were encountered: