-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[manual] Merge release/8.0-staging into release/8.0 #107578
Merged
carlossanlop
merged 23 commits into
dotnet:release/8.0
from
carlossanlop:release/8.0-staging
Sep 10, 2024
Merged
[manual] Merge release/8.0-staging into release/8.0 #107578
carlossanlop
merged 23 commits into
dotnet:release/8.0
from
carlossanlop:release/8.0-staging
Sep 10, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on macOS (dotnet#105117) * Disable W^X on x64 in rosetta based container The docker on macOS Arm64 uses Rosetta to run x64 containers. That has an effect on the double mapping. The Rosetta is unable to detect when an already executed code page is modified. So we cannot use double mapping on those containers. To detect that case, this change adds check that verifies that the double mapping works even when the code is modified. Close dotnet#102226 * Rework based on PR feedback * Check only for Rosetta * Enable the rosetta check for x86 too This will help WINE running 32 bit code under rosetta emulation on macOS. --------- Co-authored-by: Jan Vorlicek <[email protected]>
…ence-packages build 20240815.1 (dotnet#106626) Microsoft.SourceBuild.Intermediate.source-build-reference-packages From Version 8.0.0-alpha.1.24372.3 -> To Version 8.0.0-alpha.1.24415.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Initial fix for the type not being read bug. * Addressed initial feedback to fully fix the bug. --------- Co-authored-by: Ivan Diaz <[email protected]>
…xception handler (dotnet#106221) * Remove UnhandledException handler from MemoryCache to avoid deadlock. * Update Sys.RT.Caching csproj for servicing build.
* Switch build x64 image to Azure Linux 3.0 * Add remaining (existing) images * Remove accidental 9.0 * Fix BundleLegacy.TestNetCoreApp3xApp Stop relying on ICU - this is irrelevant to what the test targets. --------- Co-authored-by: Elinor Fung <[email protected]>
… to a keyed parameter (dotnet#106877) * Do not allow a non-keyed service to be injected into a keyed parameter * Fix test issue on NetFx * Add feature switch for compat: Microsoft.Extensions.DependencyInjection.AllowNonKeyedServiceInject * Enable servicing Microsoft.Extensions.DependencyInjection --------- Co-authored-by: Steve Harter <[email protected]> Co-authored-by: Eric StJohn <[email protected]>
…iptor.ImplementationInstance\Type\Factory if a keyed service (dotnet#106841) * Return null instead of throwing in ServiceDescriptor.ImplementationInstance\Type\Factory if a keyed service * Enable servicing Microsoft.Extensions.DependencyInjection.Abstractions --------- Co-authored-by: Eric StJohn <[email protected]>
…ease/8.0-staging [automated] Merge branch 'release/8.0' => 'release/8.0-staging'
…ild 20240903.2 (dotnet#107297) Microsoft.DotNet.HotReload.Utils.Generator.BuildTool From Version 8.0.0-alpha.0.24402.1 -> To Version 8.0.0-alpha.0.24453.2 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Disable MD5 tests on Azure Linux * Handle disabled algorithms on Azure Linux * Fix MD5 failures on Azure Linux in System.Security.Cryptography.Pkcs * Change BuildWithFactoryReadDirect to not use RSA+MD5 * Add Azure 3.0 helix test --------- Co-authored-by: Rich Lander <[email protected]>
Starting on macOS Sequoia, at least in beta, SecKeychainitemCopyKeychain no longer returns errSecNoSuchKeychain for ephemeral keys. Instead, it returns errSecInvalidItemRef. This adds the error code in the handling logic for when we need to add an ephemeral key to the target keychain. Co-authored-by: Kevin Jones <[email protected]>
dotnet#107161) * Avoid package dependencies on libraries in the shared framework (dotnet#106172) * Avoid package dependencies on libraries in the shared framework We can avoid these dependencies since we can count on the library being part of the shared framework. Fewer dependencies means less packages downloaded, less for customers to service, less copied into the output directory when serviced. * Add warning code. * Address feedback * Add an option to enable servicing for transitive dependencies * Enable all packages that removed dependencies * Add additional packages required for up-stack servicing * Permit settting ServiceTransitiveDependencies in projects as well
…struct (dotnet#107198) * Fix error when returning zero sized struct * Add test * Fix x64 errors --------- Co-authored-by: Jeremi Kurdek <[email protected]>
The recently added AVX support in hardware exception handling path on macOS x64 has introduced a problem when running under Rosetta. When we extract the floating point part of the context of the failing thread, the thread can have AVX or AVX512 active, or none of these. The code accidentally leaves CONTEXT_XSTATE set on the context even when no AVX was enabled on the thread. Rosetta doesn't support AVX, so having CONTEXT_XSTATE set in the context flags can lead to later call to RtlRestoreContext attempting to set ymm registers using instructions that Rosetta cannot emulate and the app crashes due to that. This doesn't happen in .NET 9, since we always clear the CONTEXT_XSTATE before exception handling stack unwinding. But in .NET 8, this causes stack overflow under Rosetta, since the attemt to execute the ymm instruction triggers the hardware exception handling again and again. Co-authored-by: Jan Vorlicek <[email protected]>
dotnet#106701) Co-authored-by: Tanner Gooding <[email protected]>
Co-authored-by: EgorBo <[email protected]>
carlossanlop
added
Servicing-approved
Approved for servicing release
area-codeflow
for labeling automated codeflow
labels
Sep 9, 2024
… enabled again for the October release.
/ba-g The only expected failure is the one below, since we reset System.Diagnostics.EventLog to false in the last commit in this PR so we don't build it again, but it has not yet been released to nuget (latest is 8.0.0).
|
This was referenced Sep 11, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge commit!