Goofy progress formatting when warning logged

[bergren2]

I don't have a solution/PR in mind for this, but wanted to get it on your radar. Basically the logging trips up how the progress counter operates and leaves a "ghost" on the first line.

Cloning repo 1/17: 'repo/name' (node:7736) ExperimentalWarning: The fs.promises API is experimental
Cloning repo 11/17: 'another/repo'

[rehret]

Good catch. This should be easy to fix.

[rehret]

Do we have a way to reproduce this? I have a fix in mind, but I'll want to test it.

[bergren2]

Could we try logging something directly, or is that too hacky? I don't remember what specifically caused that message above to get logged, and I haven't seen it since logged this either. :/

[rehret]

Okay. I'll see what I can come up with.

[rehret]

This can be reproduced by using Node >10.0.0. Also, I think the fix is more complicated than I originally thought. There's not an exception being thrown here. It's actually the Node process writing to stdout when the fs.promises API is used.