Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show more logging information after an inactivity timeout during install #1240

Closed
vjpr opened this issue Jun 22, 2018 · 4 comments · Fixed by #2615
Closed

Show more logging information after an inactivity timeout during install #1240

vjpr opened this issue Jun 22, 2018 · 4 comments · Fixed by #2615

Comments

@vjpr
Copy link
Contributor

vjpr commented Jun 22, 2018

Usually when I have a bad connection, the resolving step freezes.

It would be good to have some more info in the default logger.

$ pnpm i -S eslint-plugin-import
Resolving: total 48, reused 48, downloaded 0

Maybe after 5 seconds of inactivity, it could show an additional line to indicate what it is stuck on.

Resolving: total 48, reused 48, downloaded 0
> Trying to download package 'foo' for X seconds.

And X seconds could increment.

@zkochan
Copy link
Member

zkochan commented May 2, 2020

Another possible solution would be to allow users to switch reporting to a more verbose one. So during installation, you could press some key and it would change the reporter to print all the debug logs.

@kamilchm
Copy link

kamilchm commented Jun 4, 2020

Is there a way to see some more info right now?
I'm testing pnpm on my project and can't download anything. I tried many times, waiting for XX minutes and everything I see is:

Resolving: total 2112, reused 2112, downloaded 0

How can I check what's going on?

@zkochan
Copy link
Member

zkochan commented Jun 4, 2020

I think most frequently this happens when a request fails and pnpm tries to repeat it over and over.

To get more info, the only way is to run the command with the --reporter ndjson option.

I think what we can do pretty easily is to add some info or warning messages when a request fails.

@zkochan
Copy link
Member

zkochan commented Jun 8, 2020

🚢 5.1.5

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

Successfully merging a pull request may close this issue.

3 participants