-
Notifications
You must be signed in to change notification settings - Fork 255
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
[Bug]: Custom kernel breaks nuget #11995
Comments
Hi @Killfrra , may I know if you have run restore successfully from source nuget.org on the same machine before? BTW, could you try to add a package from a local source (which contains the package you'd like to install, so it will definitely run successfully)? And check if the |
Yes
The URL opens fine in the browser
Unfortunately, I can't do it right now. |
@Killfrra I'm not certain how to intepret your last comment. Are any you still facing any issues? |
Yes, I still have this problem. I found a workaround but I want nuget
|
We can consider that. As an immediate solution please consider changing the output of what the OSDescription returns to a format that wouldn't break the headers. |
would be great if you share the workaround for this issue. |
I'm also encountering this issue, and it's making the dotnet nuget tooling near completely unusable. What workaround did you find for the problem, save booting from a generic kernel? |
It's awkward and wild, but yes, booting with generic kernel |
That's a shame. I was hoping there was some other workaround. |
Hi, is there any news on this? Any workaround? |
I'm unsure where exactly .NET's This will let you mitigate until the above pull request is merged and shipping to customers. |
The fix should be released in NuGet 6.5, which will be in the .NET 7.0.200 SDK. Hopefully it'll be in the nightly build SDKs within a week. |
Hi zivkan, Best, |
Due to major CI issues in January, I missed the deadline for NuGet 6.5, so it'll be in NuGet 6.6. I don't know how .NET SDK preview numbers work (what date does 23108.17 correspond to?). Anyway, if you run |
We just merged some docs about this in the PR guidelines for the SDK - @zivkan wanna take a look and see if that helps? |
So, it looks like it's from yesterday, the 8th of February. So it certainly has a 6.6 build of NuGet. @cbaal83 can you please run this and tell me what the program output is? using System.Net.Http.Headers;
using System.Runtime.InteropServices;
var os = RuntimeInformation.OSDescription;
os = os.Replace("(", "\\(").Replace(")", "\\)");
Console.WriteLine("OSDescription: " + os);
ProductInfoHeaderValue userAgent = new("(" + os + ")");
Console.WriteLine("User-Agent: " + userAgent); |
Unfortunatly, i can't run this. Unfortunately i can't easily switch to another kernel. Does the Preview-Package install a system-wide version of nuget? Because the latest and greatest i was able to find online was "6.4.0.123", which is a version iam running using mono.... |
The original post in this issue shows they got 2 lines of error, the first was the "Unable to load the service index", and the second one explained why "The format of value ...". Do you not get a second error, explaining why the service index couldn't be downloaded? Can you try restoring at a higher verbosity level? Although the code sample doesn't need any packages, so I would have hoped that NuGet 6.4 maps to the .NET SDK 7.0.1xx, so it's not expected for the 7.0.300 preview to have it. .NET SDK 7.0.2xx will have NuGet 6.5, and .NET SDK 7.0.300 will have NuGet 6.6. We all increment versions are the same pace, it's just we have different versioning schemes. However, it also appears that the dotnet/sdk is not getting NuGet's 6.6 updates in its release/7.0.3xx branch: https://github.com/dotnet/sdk/blob/31945c5e5c1e85e289efd3d222fd9f76b42a3293/eng/Version.Details.xml#L108 @baronfel do you know if sdk needs to update its darc subscriptions to get the vs17.6 channel into the 7.0.3xx branch? The first NuGet 6.6 insertion into sdk's main branch (8.0.1xx) was 8 days ago: dotnet/sdk@bc5bc9a |
|
@zivkan
Best, //EDIT: Sorry, forget about the verbose restore:
|
@cbaal83 sorry about all the back-and-forth. Could you also try setting the environment variable |
I can't see any difference. Have i dont something wrong? :D Best, |
No, I don't know why the error message isn't reporting any additional information. The problem getting NuGet updates in the .NET SDK 7.0.3xx builds has been resolved, so if you try a new nightly build of the SDK, hopefully it will work. If you continue to have problems, then it's almost certainly unrelated to the customer kernel, so needs to be handled in a different issue. |
Ha, i just installed dotnet-sdk-7.0.300-preview.23112.4-x64.deb.
Looks like it's finally working again!! Thank you very much. |
NuGet Product Used
dotnet.exe
Product Version
.NET SDK Version: 6.0.302 Commit: c857713418
Worked before?
.NET SDK Version: 6.0.302 Commit: c857713418
Impact
It's more difficult to complete my work
Repro Steps & Context
It would be nice to be able to disable the sending of unnecessary information through the UserAgent.
-- from dotnet/sdk/blob/main/src/Cli/dotnet/Telemetry/TelemetryCommonProperties.cs
In addition to what is shown in the "verbose logs", performing
dotnet restore
in a project that already has aPackageReference
in .csproj gives an error:error NU1301: Unable to load the service index for source https://api.nuget.org/v3/index.json.
Verbose Logs
The text was updated successfully, but these errors were encountered: