-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
.NET October 2024 Update - .NET 8.0.10, .NET 6.0.35 #9532
Comments
Are you getting the link from the .NET website or somewhere else @MikeFarrington? I just tested with https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-8.0.403-windows-x64-installer and downloaded a 212 MB file. |
I tried both the .NET website, and from the github release page. I also tried the link in your comment. All results are the same. CDNs are of course regional, so, maybe I need to wait for it to propagate fully or something. Edit To Add: Sorry, it looks like my browser was acting up. Restarting Firefox cleared it up. Sorry, I've never had that happen before. |
I have the same problem. Installed 8.0.0 - 8.0.8 + SDK, different machines, no problem. Now: 0 Bytes, 128KB, 192KB, via Github 48KB. Tried to install the newest SDK. PS: Looks like a FireFox-Problem. Chrome - no problem, 212 MB, installation works. |
Doesn't appear to have the MacOS fix that without it, means that any Mac with Sequoia on it is non-functional with .net and a major blocker and was promised for this release. |
Was also searching around. Just saw the PR that added it into the known issue doc. I just let a friend on 15.0.1 run |
8.0.403 was just released that does fix this. But you need to run: dotnet dev-certs https --clean And then you should be back in business. |
It appears the CVE for System.Text.Json was published incorrectly, the patched version is listed as 8.0.10 - it should be 8.0.5; unless there is another pending nuget push for that package. |
Thanks a lot for flagging this. I have updated our advisories with correct versions. |
Hey, I'm quite inexperienced with docker so this might be pebkac issue. I have this dockerfile and with SDK 8.0.402 docker build is working perfectly fine. (mcr.microsoft.com/dotnet/sdk:8.0.402) However when using image mcr.microsoft.com/dotnet/sdk:8.0 (I assume this refers to current image so 8.0.403) then I get issue, somewhere in the build "dotnet devcerts https --export-path /root/.aspnet/https/something.client.pem --format Pem --no-password" is called. And this gives error that the path /root/.aspnet/https does not exist. Is something changed here? Or is something changed with setting APPDATA or HOME env var (this is also used to set the --export-path in the build)? |
Hello, Just to report that we have started to encountered tests errors after freshly pulling the 8.0.403 image. Our Dockerfile is making use of dotnet/sdk 8.0 (ff705b99a06144190e2638f8ede64a753915df5ea27fff55f58d0eb5f7054b0b). In particular, some check happened to fail the pipeline regarding the instanciation of an This is the stacktrace
This is the BaseTestClass that allows child classes to resolve some services
|
We are experiencing a very similar issue. Our docker build process started failing because the dotnet dev-certs call was failing. After some troubleshooting (no code changes from our side) we realized that .NET had a new version and other people were experiencing the same problem. Is there any way to temporarily fix this? Or should we wait for a new release? |
Added this steps to our build and did not fix the issue. Had to use FROM mcr.microsoft.com/dotnet/sdk:8.0.402 AS build We are not using Mac OS (docker image is linux based) |
.NET 8.0.8 and .NET SDK 8.0.400 after patch update the application failing with exception could not load file or assembly Microsoft.AspNetCore.SignalR.Client.Core etc.. We load all dlls from installation location and with the new patch update causing issues on client machines and forcibly asking for upgrade. Microsoft.AspNetCore.SignalR.Client.Core should be update to version 8.08, see exception msg: "Could not load file or assembly 'Microsoft.AspNetCore.SignalR.Client.Core, Version=8.0.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' |
Since upgrading to .NET 8.0.10, our application has encountered a breaking issue. Is anyone else experiencing this, or have found a solution? It might be related to Microsoft Security Advisory CVE-2024-43483. Here’s the code that’s now throwing an exception:
|
@BizzMine-PJ replacing |
.NET 6 and above replacing "EntriesCollection" with "StringKeyEntriesCollection" fixed this issue.. |
When upgrading from 6.0.133 to 6.0.135 our builds fail with a bunch of:
The few projects that depend on System.Text.Json depend on version 8.0.5. |
@BizzMine-PJ - this broke a live system for us as the LTS runtime used by Azure was silently updated to 8.0.10. This would have been far less impactful had this been mentioned somewhere on the release notes, as we were trying to hunt down what the issue was. Can changes like this be documented more fully in future on release notes please? |
Is this issue being discussed/tracked anywhere? We are unable to update to latest SDK due to this issue. |
Team, as initially reported in this .NET issue comment, there seems to be a breaking change in the libraries for ARMv7 platforms, resulting in the following error:
This issue has also been replicated in Radarr issue #10653 and SynoCommunity issue #6309 for users on Synology platforms with ARMv7 processors after upgrading from packages using .NET 6.0.32. Could this be investigated and resolved? |
closing in favor of #9599 |
.NET October 2024 Update
Release Notes
Status
Issues
Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Known Issues
[GHSA-f32c-w444-8ppv] Microsoft Security Advisory CVE-2024-43484 | .NET Denial of Service Vulnerability github/advisory-database#4883
[GHSA-qj66-m88j-hmgj] Microsoft Security Advisory CVE-2024-43483 | .NET Denial of Service Vulnerability github/advisory-database#4884
PRs to be merged. Once they are merged, NuGet should have the correct versions updated. If you have dependabot PRs open due to this, we recommend ignoring them until the corrected advisories are published on GitHub
The text was updated successfully, but these errors were encountered: