-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NuGet.Commands.LockFileBuilder KeyNotFoundException Exception #12464
Comments
Appears to be broken in preview version 6.6.0.20 as well
|
Looks like there have been some recent commits to |
@kpspence can you provide a simple repro that exhibits this error? When I put together a trivial project with PackageReferences it does not happen. I'd be interested to see what combinations of packages cause it. |
@jeffkl Please see https://github.com/kpspence/NugetBugKeyNotFound This was the minimum I could get to and have it still break. It does break consistantly on the docker build on both Jenkins and my desktop. It is an interaction of the following packages:
And the following package versions:
|
@kpspence thank you that helps tremendously! I will investigate.... |
Nbehhejjj |
I started receiving the same error and stack trace for <CentralPackageTransitivePinningEnabled>false</CentralPackageTransitivePinningEnabled> |
FYI, I think I've found a code change that is necessary to fix this. I'm working on opening a PR and adding a test case for this. |
Not sure what is going on yet, but we're seeing the same callstack on 17.9.5 with the fix in PR 5293 applied. Either there's another scenario, or the fix is for a different situation, or the fix doesn't cover all the cases. I will have to debug tomorrow. |
Hi @KirillOsenkov, is it possible by any chance to provide a public repro for it? |
Unfortunately the repro disappeared and I couldn't reproduce it any more. If I ever run into this again I'll investigate and will ping you if it's related to the algorithm you've fixed. Thanks for fixing this! |
all I know is that the C:\Users\username\appdata\roaming\NuGet\NuGet.Config on the user's machine had an entry to disable a package source that was important:
With this entry all sorts of weird problems were happening. We found and removed the entry, and now we can't get it to repro even if we add it back. |
NuGet Product Used
dotnet.exe
Product Version
dotnet 7.0.201; nuget 6.5.0.136
Worked before?
dotnet 7.0.101; nuget 6.4.0.117
Impact
It's more difficult to complete my work
Repro Steps & Context
Error
Failure Setup - Docker build
From mcr.microsoft.com/dotnet/sdk:7.0.201-bullseye-slim
Step 13/57 : RUN dotnet nuget --version
NuGet Command Line
6.5.0.136
Step 14/57 : RUN dotnet --version
7.0.201
Step 56/57 : RUN dotnet restore -v diag "Source/src/spc/SpcService/SpcService.csproj"
Exception Details
Successful Setup - Docker build
mcr.microsoft.com/dotnet/sdk:7.0.101-bullseye-slim
Step 13/57 : RUN dotnet nuget --version
NuGet Command Line
6.4.0.117
Step 14/57 : RUN dotnet --version
---> Running in 3937be4b4697
7.0.101
Step 56/57 : RUN dotnet restore -v diag "Source/src/spc/SpcService/SpcService.csproj"
Failed-7.0.201.txt
Succeed-7.0.101.txt
Verbose Logs
The text was updated successfully, but these errors were encountered: