Open jackwilsdon opened 9 months ago
From what I can tell, this is caused by this code (Scan
only returns when it finds a newline):
Not sure what the right fix is, as it seems like pkg/util/log
doesn't have any support for logging without a newline.
@jackwilsdon Thanks for the analysis! We will take a look at a fix. I had previously assumed that this was an issue with the library we were using for the shell emulation, but you're probably right in that it's the scanner using the ScanLines
function to tokenize the reader output.
@jackwilsdon While not a solution for this particular problem, I've found that read -p "Some prompt here: "
works as expected in commands. The read values can then be passed into DevSpace using the --var
flag. Hope that's helpful.
What happened? Text printed from a pipeline is not output to the terminal until a newline is reached.
What did you expect to happen instead?
Text should be printed without needing a newline.
How can we reproduce the bug? (as minimally and precisely as possible)
devspace.yaml
:devspace run-pipeline test
Local Environment:
Anything else we need to know?
This is a bigger issue when using
read -p "Some prompt here: "
, as the prompt doesn't appear until the user has hit enter (completing theread
).