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.

`dotnet new` does not support `--ignore-failed-sources`

See original GitHub issue

Describe the bug

The dotnet new invocation should honor --ignore-failed-sources either directly or through ENV settings of some sort

To Reproduce

Have a nuget feed in your global config that requires integrated auth. Then dotnet new <something> and you’ll see a failure:

The template "GitHub Actions workflow for .NET Core" was created successfully.
Error: Failed to read package information from NuGet source https://REDACTED/nuget/v3/index.json.

In this scenario where dotnet new is doing a restore immediately after it might be good to default to ignore-failed-sources immediately anyway.

Issue Analytics

State:
Created 2 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

timheuercommented, Feb 2, 2022

Yes @vlada-shubina --no-update-check worked!

0reactions

JanKrivanekcommented, Mar 29, 2022

@timheuer the default behavior now (no switch, env var or so is needed) is that nuget feeds reading errors are debug only. Error is logged only if package was not found in any feed.