kpm restore fails to proceed to fallback sources when there is an error in the first listed feed about aspnetcore

[itsananderson]

I forgot to mention, but when I disable that package source, kpm restore works as expected

[glennc]

Which feed did you disable to make it work? The MyGet feed is public as of this morning, so you should be able to use it without any auth getting in the way.

[itsananderson]

I disabled my private NuGet feed (which uses Microsoft federated auth). I didn't touch the MyGet or nuget.org feeds

[Alxandr]

I have something of the same problem. I get InternelServerError on one of the feeds, and that just crashes the whole restore.

[Praburaj]

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

[Praburaj]

Updating the title of the bug to reflect the issue.

[Praburaj]

This issue was moved to aspnet/dnx#1018