Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

(3.3.5) Progress bar seems to be broken on Windows CMD #9755

Closed
laggingreflex opened this issue Sep 25, 2015 · 23 comments
Closed

(3.3.5) Progress bar seems to be broken on Windows CMD #9755

laggingreflex opened this issue Sep 25, 2015 · 23 comments

Comments

@laggingreflex
Copy link
Contributor

I'm on npm@3.3.5 and this is what npm install xxx outputs to console on Windows CMD console:

Text (full) :

▄ ╢░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
▐ ╢░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadIdealTree → cloneCurr ▄ ╢███████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadRequestedDeps → addNa ▌ ╢██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadRequestedDeps → reque ▀ ╢██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadRequestedDeps → netwo ▄ ╢██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadRequestedDeps → netwo ▌ ╢██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadRequestedDeps → netwo ▀ ╢██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:fsevents → networ ▀ ╢████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:fsevents → 304    ▐ ╢████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:fsevents → instal ▌ ╢████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
npm WARN install Couldn't install optional dependency: Unsupported
loadDep:fsevents          ▌ ╢████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:minimatch         ▀ ╢████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:once              ▀ ╢██████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadExtraneous            ▀ ╢██████████████████████████░░░░░░░░░░░░░░░░░░░░░░░╟

It seems to be not being able to clear-line and instead goes to next line to print the "progess"..

Searched and saw some similar issues being discussed in #8812 & #8761 but I'm guessing this Windows issue is different than those?

@Stanzilla
Copy link

Mine looks like that, both in cmd and ConEmu

cmder_2015-09-26_23-25-40

cwindowssystem32cmd exe_-_vagrant__ssh_2015-09-26_23-34-07

@web20opensource
Copy link

image

@Stanzilla
Copy link

@iarna any idea what could cause this?

@iarna
Copy link
Contributor

iarna commented Oct 15, 2015

You are somehow not using a unicode font? Or there's some way that I was unware of to disable unicode support in cmd?

@Stanzilla
Copy link

No, there is no unicode on/off setting and I tried a few different fonts and all of them had that problem, Lucida Console, Consolas...etc.

@Stanzilla
Copy link

@web20opensource
Copy link

Thanks @Stanzilla

@Stanzilla
Copy link

It works in PuTTY though, I haven't managed to get it working in either cmd or ConEmu.

@laggingreflex
Copy link
Contributor Author

Apart from unicode characters not rendering (presumably rendering "a"s for █ blocks, which actually isn't the case with me as posted originally), what about the issue of them appearing in multiple lines like that? I assume they're supposed to be re-rendered in the same line showing the progress, but instead are getting printed on new lines?

Or could these two issues actually be related? Like some new line character not being rendered kind of issue?

@lizimeow
Copy link

i met the same situation with you..
Do you settle this matter now?QAQ

@Stanzilla
Copy link

Sort of, you have to use PUTTY if you want it to look right.

@yongtw123
Copy link

A similar issue #10648 refers to here https://github.com/iarna/gauge/issues/5 as the cause. It's about the code page.

@Stanzilla
Copy link

You can change the codepage all you want on Windows, it doesn't fix this. Mine is actually set to Unicode on the screenshots.

@yongtw123
Copy link

@Stanzilla Have you tried this? http://stackoverflow.com/a/388500 It works for me but I suspect there could be ramifications.

@Stanzilla
Copy link

@yongtw123 yep, didn't fix it for me. did it for you?

@ghost
Copy link

ghost commented Dec 5, 2015

This problem also confused me.

    npm@3.3.12
    win7

It's hard to use UTF-8 as a default coding page.

If it's not possible to change back to the v2 style progress bar officially, is it possible to give us a hint how to do it ourself ?

BTW, after running 'chcp 65001', it throws following error:
npm_cp_65001

while it works well after 'chcp 437'.

Thanks.

@ghost
Copy link

ghost commented Feb 9, 2016

The difficult part happens in changing the default system characters to the new old.

e.g. Orginally using Chinese, then chaning to UTF-8 will result in all file names in Chinese will be messed up.

Alternatively, if it can show progress percentage instead of progress bar, or just a switch to turn it off, it will be very helpful.

Thanks.

@lovanwubing
Copy link

A simple solution is to upgrade node js to latest version 6.6.0. It works for me on windows 10.

@rempatterson
Copy link

I desparately want to to unsubscribe. How can I do it? I think you are reaching me at my email alias of 'patterson@computer.org', although it is possible you are writing me directly at 'bill.patterson1@comcast.net. Ether way, I am not prepared for the volume of email that I am getting.

Thank you.

----- Original Message -----

From: "Bing" notifications@github.com
To: "npm/npm" npm@noreply.github.com
Sent: Saturday, May 14, 2016 10:57:50 AM
Subject: Re: npm/npm Progress bar seems to be broken on Windows CMD (#9755)

A simple solution is to upgrade node js to latest version 6.6.0. It works for me on windows 10.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

@laggingreflex
Copy link
Contributor Author

@lovanwubing node latest is 6.1, no? I have that (and also I'm on Win10) but issue still persists. Did you mean nightly builds? But even in nighly builds I don't see a v6.6

Also I like to point out that the issues detailed in this thread are actually two different ones. The first one (with which I started the thread) was that the progress isn't displayed in a single line, but every change in animation (the rotator, the bar) displays in a new line.

The second issue, as pointed out by @Stanzilla and others is the font issue. I personally don't have this issue. But others seem to have both.

Are these two related?


@rempatterson visit this page and try the unsubscribe button on the right --->

@daddie888
Copy link

I got both problems after upgrading to Ruby MRI 2.3.0 on W7. Was only with MRI, not jRuby and only in Conemu, CMD was fine. Got rid of the problem by unchecking the Settings/Features/Inject ConEmuHk checkbox. Hope it helps. The combination Ruby-ConEmu rocks..

@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants