-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[main] Source code updates from dotnet/dotnet #118914
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
Conversation
[[ commit created by automation ]]
Updated Dependencies: Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.Analyzers, Microsoft.CodeAnalysis.CSharp, Microsoft.Net.Compilers.Toolset (Version 5.0.0-2.25418.105 -> 5.0.0-2.25419.104) Microsoft.CodeAnalysis.NetAnalyzers (Version 10.0.0-preview.25418.105 -> 10.0.100-rc.1.25419.104) Microsoft.DotNet.ApiCompat.Task, Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport (Version 10.0.100-rc.1.25418.105 -> 10.0.100-rc.1.25419.104) Microsoft.DotNet.Arcade.Sdk, Microsoft.DotNet.Build.Tasks.Archives, Microsoft.DotNet.Build.Tasks.Feed, Microsoft.DotNet.Build.Tasks.Installers, Microsoft.DotNet.Build.Tasks.Packaging, Microsoft.DotNet.Build.Tasks.TargetFramework, Microsoft.DotNet.Build.Tasks.Templating, Microsoft.DotNet.Build.Tasks.Workloads, Microsoft.DotNet.CodeAnalysis, Microsoft.DotNet.GenAPI, Microsoft.DotNet.GenFacades, Microsoft.DotNet.Helix.Sdk, Microsoft.DotNet.PackageTesting, Microsoft.DotNet.RemoteExecutor, Microsoft.DotNet.SharedFramework.Sdk, Microsoft.DotNet.XliffTasks, Microsoft.DotNet.XUnitExtensions (Version 10.0.0-beta.25418.105 -> 10.0.0-beta.25419.104) Microsoft.DotNet.Cecil (Version 0.11.5-alpha.25418.105 -> 0.11.5-alpha.25419.104) Microsoft.DotNet.XUnitAssert, Microsoft.DotNet.XUnitConsoleRunner (Version 2.9.3-beta.25418.105 -> 2.9.3-beta.25419.104) Microsoft.NET.Sdk.IL, Microsoft.NETCore.App.Ref, Microsoft.NETCore.ILAsm, runtime.native.System.IO.Ports, System.Reflection.Metadata, System.Reflection.MetadataLoadContext, System.Text.Json (Version 10.0.0-rc.1.25418.105 -> 10.0.0-rc.1.25419.104) NuGet.Frameworks, NuGet.Packaging, NuGet.ProjectModel, NuGet.Versioning (Version 7.0.0-preview.1.41905 -> 7.0.0-preview.1.42004) System.CommandLine (Version 2.0.0-rc.1.25418.105 -> 2.0.0-rc.1.25419.104)
|
@ViktorHofer analyzer related errors here. |
|
@ericstj this is the package layout:
That should be correct, right? |
|
Error is So it is trying to find |
|
Looks like a hardcoded path here - Lines 54 to 58 in 749340b
I'll update that. I think the new package layout from @ViktorHofer's change is more correct. This project voided the warranty by grabbing direct files like this, so it's responsible for the break. cc @jkoritzinsky |
|
I'm fine with whatever changes need to be made to fix the build. For reference, we ref this project in this way because we have a diagnostic suppressor for a case where one of the analyzers from there would break SG interop and we didn't want users getting sent down the wrong path. |
|
Yep - it's clear why you did this, only called out responsibility here in case we needed to consider which side should change to fix it. One thing that could make this less fragile would be a package provided for referencing an analyzer, or targets within the analyzer package (which knows its own internal layout) that could raise the reference when a property is set. I'm not sure I'd bother with either since this sort of move/rename is unlikely to happen again. |
[[ commit created by automation ]]
Updated Dependencies: Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.Analyzers, Microsoft.CodeAnalysis.CSharp, Microsoft.Net.Compilers.Toolset (Version 5.0.0-2.25419.104 -> 5.0.0-2.25419.113) Microsoft.CodeAnalysis.NetAnalyzers, Microsoft.DotNet.ApiCompat.Task, Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport (Version 10.0.100-rc.1.25419.104 -> 10.0.100-rc.1.25419.113) Microsoft.DotNet.Arcade.Sdk, Microsoft.DotNet.Build.Tasks.Archives, Microsoft.DotNet.Build.Tasks.Feed, Microsoft.DotNet.Build.Tasks.Installers, Microsoft.DotNet.Build.Tasks.Packaging, Microsoft.DotNet.Build.Tasks.TargetFramework, Microsoft.DotNet.Build.Tasks.Templating, Microsoft.DotNet.Build.Tasks.Workloads, Microsoft.DotNet.CodeAnalysis, Microsoft.DotNet.GenAPI, Microsoft.DotNet.GenFacades, Microsoft.DotNet.Helix.Sdk, Microsoft.DotNet.PackageTesting, Microsoft.DotNet.RemoteExecutor, Microsoft.DotNet.SharedFramework.Sdk, Microsoft.DotNet.XliffTasks, Microsoft.DotNet.XUnitExtensions (Version 10.0.0-beta.25419.104 -> 10.0.0-beta.25419.113) Microsoft.DotNet.Cecil (Version 0.11.5-alpha.25419.104 -> 0.11.5-alpha.25419.113) Microsoft.DotNet.XUnitAssert, Microsoft.DotNet.XUnitConsoleRunner (Version 2.9.3-beta.25419.104 -> 2.9.3-beta.25419.113) Microsoft.NET.Sdk.IL, Microsoft.NETCore.App.Ref, Microsoft.NETCore.ILAsm, runtime.native.System.IO.Ports, System.Reflection.Metadata, System.Reflection.MetadataLoadContext, System.Text.Json (Version 10.0.0-rc.1.25419.104 -> 10.0.0-rc.1.25419.113) NuGet.Frameworks, NuGet.Packaging, NuGet.ProjectModel, NuGet.Versioning (Version 7.0.0-preview.1.42004 -> 7.0.0-preview.1.42013) System.CommandLine (Version 2.0.0-rc.1.25419.104 -> 2.0.0-rc.1.25419.113)
Updated Dependencies: Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.Analyzers, Microsoft.CodeAnalysis.CSharp, Microsoft.Net.Compilers.Toolset (Version 5.0.0-2.25419.113 -> 5.0.0-2.25420.121) Microsoft.CodeAnalysis.NetAnalyzers, Microsoft.DotNet.ApiCompat.Task, Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport (Version 10.0.100-rc.1.25419.113 -> 10.0.100-rc.1.25420.121) Microsoft.DotNet.Arcade.Sdk, Microsoft.DotNet.Build.Tasks.Archives, Microsoft.DotNet.Build.Tasks.Feed, Microsoft.DotNet.Build.Tasks.Installers, Microsoft.DotNet.Build.Tasks.Packaging, Microsoft.DotNet.Build.Tasks.TargetFramework, Microsoft.DotNet.Build.Tasks.Templating, Microsoft.DotNet.Build.Tasks.Workloads, Microsoft.DotNet.CodeAnalysis, Microsoft.DotNet.GenAPI, Microsoft.DotNet.GenFacades, Microsoft.DotNet.Helix.Sdk, Microsoft.DotNet.PackageTesting, Microsoft.DotNet.RemoteExecutor, Microsoft.DotNet.SharedFramework.Sdk, Microsoft.DotNet.XliffTasks, Microsoft.DotNet.XUnitExtensions (Version 10.0.0-beta.25419.113 -> 10.0.0-beta.25420.121) Microsoft.DotNet.Cecil (Version 0.11.5-alpha.25419.113 -> 0.11.5-alpha.25420.121) Microsoft.DotNet.XUnitAssert, Microsoft.DotNet.XUnitConsoleRunner (Version 2.9.3-beta.25419.113 -> 2.9.3-beta.25420.121) Microsoft.NET.Sdk.IL, Microsoft.NETCore.App.Ref, Microsoft.NETCore.ILAsm, runtime.native.System.IO.Ports, System.Reflection.Metadata, System.Reflection.MetadataLoadContext, System.Text.Json (Version 10.0.0-rc.1.25419.113 -> 10.0.0-rc.1.25420.121) NuGet.Frameworks, NuGet.Packaging, NuGet.ProjectModel, NuGet.Versioning (Version 7.0.0-preview.1.42013 -> 7.0.0-preview.1.42121) System.CommandLine (Version 2.0.0-rc.1.25419.113 -> 2.0.0-rc.1.25420.121)
|
@dotnet/wasm-eng seems like many wasm tests are failing with the same error here: |
|
@javiercn ptal |
|
WBT |
|
Looks like this data comes from this file -- |
|
I see these are read via https://github.com/dotnet/aspnetcore/blob/30609470fad0bdbe19f14597971542eb4de69641/src/StaticAssets/src/StaticAssetsManifest.cs#L32 I see they are generated with https://github.com/dotnet/sdk/blob/d2466ae2a65b6584444f73d0e1d5f4425ab6c77b/src/StaticWebAssetsSdk/Tasks/GenerateStaticWebAssetEndpointsManifest.cs#L11 @javiercn I suspect your change dotnet/sdk@952f759 caused this |
|
@javiercn I guess this is because you stopped setting weak ETag in Release mode, but these tests are running Release builds. This component which checks for weak ETag seems to be enabled by the presense of I can see that I can set |
|
@ericstj Yes.
|
|
@akoeplinger or @maraf can you help with the tests here? |
|
@javiercn I filed dotnet/aspnetcore#63364 because based on what I saw this might impact anyone running |
Would that be to set this property in a place like https://github.com/dotnet/runtime/blob/main/src/mono/wasm/Wasm.Build.Tests/data/Blazor.Directory.Build.props, and other props in the same directory? |
|
I've pushed a change to unblock the build |
|
Are you sure that file isn't going to be overwritten with the props files I pointed out above? I was in the middle of testing a change to the repro and had modified all the props here https://github.com/dotnet/runtime/blob/main/src/mono/wasm/Wasm.Build.Tests/data. It looks to me like these are all copied to test root, (EG: C:\scratch\helix\dotnet-backflo\workitems\Workloads-ST-Wasm.Build.Tests.HttpTests\wbt artifacts\HttpTest_Release_False_4keioy03_gim_鿀蜒枛遫䡫煉\Directory.Build.props) when building the test. |
|
When I tried this in my local repro 56a92b3 did not fix the issue, since those props are not used. The changes I suggested above do fix at least the test case I've been looking at. This is the copy I was mentioning: runtime/src/mono/wasm/Wasm.Build.Tests/Blazor/BlazorWasmTestBase.cs Lines 83 to 84 in 4b2a7d5
runtime/src/mono/wasm/Wasm.Build.Tests/Common/BuildEnvironment.cs Lines 183 to 187 in 4b2a7d5
runtime/src/mono/wasm/Wasm.Build.Tests/Common/BuildEnvironment.cs Lines 94 to 104 in 4b2a7d5
runtime/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs Lines 241 to 242 in 4b2a7d5
Maybe we need both? FWIW I also see the same sort of structure under the WASI tests, but maybe those aren't running in this build pipeline. cc @radical |
|
I have temporarily disabled this subscription https://maestro.dot.net/subscriptions?search=f7901f87-9f24-40d6-9bc1-564863937237&showDisabled=True. Will reenable after merging |
Subscription has been re-enabled. |


Note
This is a codeflow update. It may contain both source code changes from the VMR as well as dependency updates. Learn more here.
This pull request brings the following source code changes
From https://github.com/dotnet/dotnet
Updated Dependencies
Associated changes in source repos