Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`An error occurred while upgrading...` but no error message

See original GitHub issue

When running this against some of my solutions I’m getting an error message:

An error occurred while upgrading [Project Name here]

There is not information to help me diagnose why I’m getting this error. Is it possible to log out RunStatus.Output to provide some hope of solving this?

Possibly, this could be behind a --verbose flag to prevent it littering the logs for everyone?

Issue Analytics

State:
Created 2 years ago
Reactions:10
Comments:14 (5 by maintainers)

Top GitHub Comments

8reactions

specialforestcommented, Jun 8, 2022

For me the issue was coming from DotNetRunner having hardcoded 20 seconds timeout for adding a package (and restoring them): https://github.com/dotnet-outdated/dotnet-outdated/blob/master/src/DotNetOutdated.Core/Services/DotNetRunner.cs#L36

As workaround could try “–no-restore” option.

3reactions

reducktedcommented, Aug 20, 2023

I just realized that there’s already a --no-restore option 🤦‍♂️. It’s used for skipping package restore when updating packages.

I’ve come up with a different solution in #468. Rather than having a fixed timeout of 20 seconds for running the dotnet process, the timeout only applies from the time when output from the dotnet process was last received. So as long as the dotnet process is still writing something to stdout or stderr, dotnet-outdated will continue to wait for it to complete. If it doesn’t output anything for 20 seconds, then the process is aborted.