Closed feiling closed 9 years ago
If this is due to a circular dependency then it should be fixed for RTM already with: https://github.com/NuGet/Home/issues/171
This bug repros with the current dev branch.
This code has been removed so this can't repo on the latest build.
However, this indicates a logical loop in the data we are serving from nuget.org that shouldn't be there. NuGet doesn't detect these problems on the server but it should.
Leaving this issues open for today because we need to verify a recent build and investigate the problem in the data.
Please verify https://github.com/NuGet/Home/issues/571 and https://github.com/NuGet/Home/issues/544 when this bug is fixed.
we now understand and prioritize listed/unlisted correctly in the resolver and include these in the v3 feed. we need to verify this particular case against the registration1 set of registration blobs (because they contain the field "listed" instead of the cryptic not-published-in-1900 logic
We're adding addition tests at the NuGet.PackageManager level to catch these issues.
This is a bug found by a customer.
Repro steps:
install-package t4mvc
. After a while, VS will crash. With a debugger, you can see that the crash is caused by stack overflow: the call stack reaches 5000 levels. This function call is repeated ad infinitum on the call stack:This looks to me that there are somehow circular dependencies and our code doesn't detect this scenario.