[manual] Merge release/8.0-staging into release/8.0 #103253
Merged
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
…e/8.0-to-release/8.0-staging [automated] Merge branch 'release/8.0' => 'release/8.0-staging'
…sgen2 changes) (dotnet#101869) * Add check for tizen in ilc and crossgen2 (dotnet#90310) * Enable trimming for crossgen2 publishing and fix symbol bug (dotnet#91135) * Use a different crossgen2 when running crossgen2 during our build than the crossgen2 that we are shipping (dotnet#92677) * Remove explicit listing of RIDs to avoid trying to restore the runtime packs for all possible targets. Use the local targeting and runtime packs explicitly to make sure we're publishing crossgen2 with the local build. Extracted from dotnet#92826 --------- Co-authored-by: Aleksandr Shaurtaev <38426614+ashaurtaev@users.noreply.github.com> Co-authored-by: Andy Gocke <angocke@microsoft.com> Co-authored-by: Jeremy Koritzinsky <jekoritz@microsoft.com> Co-authored-by: Jeremy Koritzinsky <jkoritzinsky@gmail.com>
…ream (dotnet#102147) * Fix data race leading to a deadlock when opening QuicStream (dotnet#101250) * Fix data race leading to a deadlock. * Remove unwanted change * Code review feedback * Fix hang * Add assert * Fix potential crash * Code review feedback * Fix thrown exception.
…egs into one leg per platform" (dotnet#102097) * Merge CoreCLR-based official builds legs into one leg per platform (dotnet#92901) * Pass "is official build" variable to AllConfigurations leg in the official build. (dotnet#93078) --------- Co-authored-by: Jeremy Koritzinsky <jekoritz@microsoft.com>
… ownership to `WinHttpRequestState` (dotnet#102083) * move _cachedSendPinnedBuffer ownership to WinHttpRequestState * set GeneratePackageOnBuild & ServicingVersion
…ference-packages (dotnet#101917) * Update dependencies from https://github.com/dotnet/source-build-reference-packages build 20240501.1 Microsoft.SourceBuild.Intermediate.source-build-reference-packages From Version 8.0.0-alpha.1.24163.3 -> To Version 8.0.0-alpha.1.24251.1 * Update dependencies from https://github.com/dotnet/source-build-reference-packages build 20240507.2 Microsoft.SourceBuild.Intermediate.source-build-reference-packages From Version 8.0.0-alpha.1.24163.3 -> To Version 8.0.0-alpha.1.24257.2 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…ternals (dotnet#101979) * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240506.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24256.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240513.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24263.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240513.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24263.1 * Update dependencies from https://github.com/dotnet/source-build-externals build 20240513.1 Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24216.1 -> To Version 8.0.0-alpha.1.24263.1 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…01941) * Update dependencies from https://github.com/dotnet/emsdk build 20240506.2 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.6-servicing.24252.3 -> To Version 8.0.6-servicing.24256.2 * Update dependencies from https://github.com/dotnet/emsdk build 20240507.1 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.6-servicing.24252.3 -> To Version 8.0.6-servicing.24257.1 * Update dependencies from https://github.com/dotnet/emsdk build 20240508.1 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.6-servicing.24252.3 -> To Version 8.0.6-servicing.24258.1 * Update dependencies from https://github.com/dotnet/emsdk build 20240514.1 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.6-servicing.24252.3 -> To Version 8.0.6-servicing.24264.1 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Initial changes * Enable building in 8.0.6 release * Build netstandard 2.1 installer for RPM only * Update target build to 8.0.7
…nals build 20240519.1 (dotnet#102453) Microsoft.SourceBuild.Intermediate.source-build-externals From Version 8.0.0-alpha.1.24263.1 -> To Version 8.0.0-alpha.1.24269.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…40429.2 (dotnet#102433) Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 8.0.0-prerelease.24208.4 -> To Version 8.0.0-prerelease.24229.2 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…AvailableAsync (dotnet#102376) * Fix cancellation unregistration in DataflowBlock.OutputAvailableAsync (dotnet#99632) OutputAvailableAsync is not unregistering from the supplied CancellationToken. If a cancelable token is supplied and is long lived, each call with that token to OutputAvailableAsync will add another callback into that token, and that will continue to grow until either the token is dropped or has been cancellation requested. For a long-lived cancellation token, this is akin to a leak. The implementation was trying to be too clever in avoiding an additional continuation that was previously there. However, this continuation makes it a lot easier to avoid possible deadlocks that can occur if a cancellation request comes in concurrently with a message being pushed. Instead of trying to avoid it, just use an async method, which still incurs the extra task but does so with less allocation and greatly simplifies the code while also fixing the issue, as all cleanup can now be done in the continuation as part of the async method. * Enable DataFlow package in servicing --------- Co-authored-by: Eric StJohn <ericstj@microsoft.com>
…otnet#102159) When invoking a delegate, we were overwritting the stack slot containing the delegate object reference. In the case of invoking a delegate for a dynamic method, we were running into issues when the delegate object is collected while the method is executed because the method code is also discarded.
* [mono][infra] Fix mono-aot-cross build for linux-arm64 using biarch image (dotnet#91019) * Use host rootfs when TARGET_BUILD_ARCH matches * Don't build libraries native packages in the PGO leg (dotnet#92729) * Reenable OneLocBuild in runtime-official.yml (dotnet#95014) * Move FreeBSD CI leg to CBL-Mariner and v13 (dotnet#97038) * Use Ubuntu-22.04-based Tizen image (dotnet#98589) * Start moving over to official templates (dotnet#99433) * Start moving over to official templates * Parameterize runtime-inner-loop * Use default false for isOfficialBuild in pipeline-with-resources * Respond to PR comments * Code review comments * Use default template args * Move linux_x86, tizen_armel, and freebsd_x64 jobs to global-build.yml * Update thunktemplates.S (dotnet#100066) * Import pool providers (dotnet#100851) Import pool-providers in common variables. This should allow all stages access to the pool provider variables. * Pass templatePath to eng/pipelines/common/templates/runtimes/xplat-job.yml --------- Co-authored-by: Milos Kotlar <kotlarmilos@gmail.com> Co-authored-by: Jeremy Koritzinsky <jekoritz@microsoft.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Andy Gocke <angocke@microsoft.com> Co-authored-by: Filip Navara <filip.navara@gmail.com> Co-authored-by: Eduardo Manuel Velarde Polar <evelardepola@microsoft.com>
…ollectible LoaderAllocators (dotnet#102872) (cherry picked from commit eb84218)
When the formatted string cannot fully fit in the buffer (including its null terminator) `_vsnprint_f` should return -1. However, in the case where the number of chars was the same as the buffer size it was returning the buffer size. Co-authored-by: Jakob Botsch Nielsen <jakob.botsch.nielsen@gmail.com>
…tnet#102095) * Disable OpenSSL internal SSL_SESSION cache for clients * Attempt no. 2 * Revert "Disable OpenSSL internal SSL_SESSION cache for clients" This reverts commit 56a308e. --------- Co-authored-by: Radek Zikmund <r.zikmund.rz@gmail.com>
…e a CPU core and prevent incoming connections (dotnet#102530) * 8 fix for ipc * Update ds-ipc-pal-namedpipe.c
Backport of dotnet#100640 to release/8.0-staging /cc @carlossanlop @liveans ## Customer Impact Noisy test, impacts us. ## Regression No ## Testing ## Risk LOW, only test code change
…nd Windows servers (dotnet#102216) * Fix NegotiateStream connections between Linux clients and Windows servers (dotnet#99909) * Send the NegotiateSeal NTLM flag when client asked for ProtectionLevel.EncryptAndSign. Process the last handshake done message in NegotiateStream. In case of SPNEGO protocol it may contain message integrity check. Additionally, if the negotiated protocol is NTLM then we need to reset the encryption key after the message integrity check is verified. * Add test for the NegotiateSeal flag * Fix the test * Dummy commit * Fix the new _remoteOk logic in NegotiateStream to fire only when HandshakeComplete. If HandshakeComplete is not true, then the authentication blob will get processed with the normal flow. * Fix the value of NegotiateSeal in the final authentication message of Managed NTLM * Fix build * Remove unwanted test change --------- Co-authored-by: Filip Navara <filip.navara@gmail.com> Co-authored-by: wfurt <tweinfurt@yahoo.com>
A recent partial backport of a change to enable propagating exceptions on shutdown was missing two places in the code that were under a different condition than the global exception handling disabling that was removed. I must have made a mistake when testing that change (not setting watson registry settings properly or using a stale build). This change makes it work correctly.
…e/8.0-to-release/8.0-staging [automated] Merge branch 'release/8.0' => 'release/8.0-staging'
carlossanlop
requested review from
lewing,
radical,
pavelsavara,
kg,
BrzVlad,
kotlarmilos and
marek-safar
as code owners
carlossanlop
added
area-codeflow
hoyosjs
approved these changes
Jun 10, 2024
hoyosjs
approved these changes
Jun 10, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.