kpm restore failures on one NuGet feed shouldn't block other feeds

[MrJul]

Scenario

• Two NuGet feeds are configured.
• One NuGet feed answers correctly (it's nuget.org).
• The other one answers with non-XML content for various reasons: authentication failure, page not found, server error, not a nuget feed URL, etc.

Expected result

The bogus feed is ignored, packages are restored from the first feed.

Actual result

Nothing is restored, a message The XML file <filename>.dat is corrupt appears.

How to reproduce

Add any website, such as bing.com as a secondary NuGet feed.

Real world scenario

We're using NuGet.org and a private TeamCity feed, which returns a HTTP 204 NoContent response when a package is not found. Thus, we can't restore any package.

[davidfowl]

That's fixed in later versions of kpm. We only cache 200 responses.

[MrJul]

Thank you for the quick answer.
Can we easily update the various KRE packages that come with VS2015 Preview (in %programfiles(x86)%\Microsoft Web Tools\Kre) to nightly builds?

[Praburaj]

This is a dup of aspnet/dnx#1018. I can still reproduce the issue and below is some repro steps I copied from the bug.

I can still reproduce this - For example if I have a package X in my project.json dependencies and I try to do a kpm restore -s http://notexistingfeed.com/api/v2 -s https://nuget.org/api/v2 (Note: This command has multiple feeds and the first one a non-existing feed). When there is an error (404/500 etc) in the first feed kpm restore fails and does not proceed to the fallback sources. For instance the same is handled differently in older nuget where it falls back.

The source at NonExisting [http://notexistingsite.com/api/v2] is unreachable. Falling back to NuGet Local Cache at C:\Users\prabht\AppData\Local\NuGet\Cache