-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Merging internal commits for release/6.0 #47652
Merging internal commits for release/6.0 #47652
Conversation
Merge from public release/6.0 to internal/release/6.0 and resolve conflicts if necessary
…ng/internal/dotnet-runtime This pull request updates the following dependencies [marker]: <> (Begin:7745f62d-e15b-4ba3-39b3-08d960f4ca81) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime - **Subscription**: 7745f62d-e15b-4ba3-39b3-08d960f4ca81 - **Build**: 20230323.11 - **Date Produced**: March 24, 2023 6:12:38 PM UTC - **Commit**: 1e620a42e71ca8c7efb033fd525f04be5fa701fe - **Branch**: refs/heads/internal/release/6.0 [DependencyUpdate]: <> (Begin) - **Updates**: - **Microsoft.Internal.Runtime.AspNetCore.Transport**: [from 6.0.16-servicing.23170.9 to 6.0.16-servicing.23173.11][1] - **Microsoft.NET.Runtime.MonoAOTCompiler.Task**: [from 6.0.16 to 6.0.16][1] - **Microsoft.NET.Runtime.WebAssembly.Sdk**: [from 6.0.16 to 6.0.16][1] - **Microsoft.NETCore.App.Ref**: [from 6.0.16 to 6.0.16][1] - **Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm**: [from 6.0.16 to 6.0.16][1] - **Microsoft.NETCore.App.Runtime.win-x64**: [from 6.0.16 to 6.0.16][1] - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 6.0.16-servicing.23170.9 to 6.0.16-servicing.23173.11][1] - **Microsoft.NETCore.Platforms**: [from 6.0.9 to 6.0.9][1] [1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GC567ff53ac7&targetVersion=GC1e620a42e7&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
…-merge-6.0-2023-04-11-1028
Hi @vseanreesermsft. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at. |
Got some Components-e2e failures, @MackinnonBuck could you take a look?
|
Looks like some tests are failing because there are errors in the console. @pavelsavara Do you know what might be happening here? From what I can tell, application functionality hasn't broken in any way other than outputting this error in the console.
|
I don't know yet. @kg @radekdoulik any thoughts ? |
|
@elinor-fung I think this is the dllimport change breaking blazor |
Looks like 6.0 didn't have the null check: dotnet/runtime#60445 Just to double check - this is a log message, not a 'crashing the world', right? |
Test failure fixed by dotnet/runtime#84740 |
no this is crashing the world when that path gets hit |
Hi @lewing. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
No description provided.