- 
                Notifications
    You must be signed in to change notification settings 
- Fork 5.2k
[manual] Merge release/8.0-staging into release/8.0 #104929
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
          
     Merged
      
      
            carlossanlop
  merged 32 commits into
  dotnet:release/8.0
from
carlossanlop:release/8.0-staging
  
      
      
   
  Jul 16, 2024 
      
    
                
     Merged
            
            [manual] Merge release/8.0-staging into release/8.0 #104929
                    carlossanlop
  merged 32 commits into
  dotnet:release/8.0
from
carlossanlop:release/8.0-staging
  
      
      
   
  Jul 16, 2024 
              
            Conversation
  
    
      This file contains hidden or 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
    
  
  
    
    Co-authored-by: Kevin Jones <[email protected]>
* Update dotnet-pgo.md Updates the instructions on how to install and use dotnet-pgo. * Update docs/design/features/dotnet-pgo.md --------- Co-authored-by: Steve Pfister <[email protected]> Co-authored-by: Jan Kotas <[email protected]>
….Reflection (#103726) Implements the API proposal detailed and approved in issue #101616. This new API will allow developers to change the entry assembly of their .NET apps on the fly, should they require it. One important scenario is app launchers. With the usage of this API, then functions like `GetEntryAssembly()` will return the right value, and thus we will be able to ensure the information is consistent and correct.
…103817) Customers who want to create native static or shared libraries (aka library mode) for nativeaot targeting ios and android were blocked by an msbuild check in the mono workload target. This check assumes if you set the NativeLib property that you want mono's version of library mode and it will error out telling you to install a specific workload. The fix adds an additional check for PublishAot != 'true' to prevent the error message from appearing when the customer wants nativeaot.
* Fix missing substitution (#103287) * Update dependencies from https://github.com/dotnet/emsdk build 2024061.3 (#103291) Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.7-servicing.24277.3 -> To Version 8.0.7-servicing.24310.3 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> * [release/8.0] Update dependencies from dotnet/emsdk (#103388) * Update dependencies from https://github.com/dotnet/emsdk build 20240612.2 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.7-servicing.24310.3 -> To Version 8.0.7-servicing.24312.2 * Update dependencies from https://github.com/dotnet/emsdk build 20240612.2 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.7-servicing.24310.3 -> To Version 8.0.7-servicing.24312.2 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> * Update dependencies from https://github.com/dotnet/emsdk build 20240613.1 (#103426) Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.7-servicing.24312.2 -> To Version 8.0.7-servicing.24313.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> * update ESRP Code Signing --------- Co-authored-by: Carlos Sánchez López <[email protected]> Co-authored-by: Larry Ewing <[email protected]> Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…#103578) * Update dependencies from https://github.com/dotnet/hotreload-utils build 20240617.1 Microsoft.DotNet.HotReload.Utils.Generator.BuildTool From Version 8.0.0-alpha.0.24271.1 -> To Version 8.0.0-alpha.0.24317.1 * Update dependencies from https://github.com/dotnet/hotreload-utils build 20240624.2 Microsoft.DotNet.HotReload.Utils.Generator.BuildTool From Version 8.0.0-alpha.0.24271.1 -> To Version 8.0.0-alpha.0.24324.2 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…03.2 (#104378) Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.7-servicing.24277.3 -> To Version 8.0.8-servicing.24353.2 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Carlos Sánchez López <[email protected]>
…ion changes in cases involving a lot of sync-over-async (#103984) * [8.0] Add a config flag to experiment with some work item prioritization changes in cases involving a lot of sync-over-async Some services that use a lot of sync-over-async were seen to experience stalls due to some priority inversion issues in work items that get queued to the thread pool. For instance, a work item W1 queues another work item W2 to the global queue and blocks waiting for a task to complete, where W2 would need to run in order to complete the task, but W2 is queued behind a number of other work items that operate like W1, and this sometimes leads to long-duration stalls. This change adds an experimental config option that when enabled, enqueues some kinds of work items to a new low-priority global queue that is checked after all other global queues. This was seen to help in some cases.
Co-authored-by: Tanner Gooding <[email protected]>
#104711) * Use latest .NET version in HttpStress runs * Revert sdk image changes * Apply to sslstress as well
….5 (#104744) 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.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 8.0.0-beta.24266.3 -> To Version 8.0.0-beta.24360.5 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
… down-level support if any parameters can't be marshalled (#104501)
…CertificateContext (#104541) Backport of #103372 and #104016 to release/8.0-staging ## Customer Impact - [X] Customer reported (#100602) - [ ] Found internally Customers developing Android apps are currently unable to use mutual TLS authentication in certain cases as the `SslStreamCertificateContext.Create(...)` method will fail to build an X509Chain instance if the certificate isn't trusted by the OS due to the limitations of the Android platform. ## Regression - [ ] Yes - [X] No ## Testing Unit tests and manual testing on Android emulator. ## Risk Low. The change is mostly limited to Android where this API doesn't currently work in many cases. --------- Co-authored-by: Tomas Weinfurt <[email protected]> Co-authored-by: Vitek Karas <[email protected]>
…08.2 (#104578) Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.8-servicing.24353.2 -> To Version 8.0.8-servicing.24358.2 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Carlos Sánchez López <[email protected]>
…to-release/8.0-staging [automated] Merge branch 'release/8.0' => 'release/8.0-staging'
…#104893) * Update dependencies from https://github.com/dotnet/hotreload-utils build 20240712.2 Microsoft.DotNet.HotReload.Utils.Generator.BuildTool From Version 8.0.0-alpha.0.24324.2 -> To Version 8.0.0-alpha.0.24362.2 * Update dependencies from https://github.com/dotnet/hotreload-utils build 20240715.1 Microsoft.DotNet.HotReload.Utils.Generator.BuildTool From Version 8.0.0-alpha.0.24324.2 -> To Version 8.0.0-alpha.0.24365.1 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
….0-staging [automated] Merge branch 'release/8.0' => 'release/8.0-staging'
* some logs * debugging the adventure * using the XSTATE_SUPPORTED macro * use minipal getcpufeatures * add conditional in MachExceptionInfo constructor * fix whitespace and remove logs * whitepace * remove conditional checks and rely on Fallthrough * remove uneeded dependencies * Remove logging that should not be there --------- Co-authored-by: Diag <[email protected]> Co-authored-by: Mikelle <[email protected]> Co-authored-by: Jan Vorlicek <[email protected]>
* Microsoft.Extensions.Configuration.Binder * Microsoft.Extensions.Configuration.FileExtensions * System.Net.Http.WinHttpHandler * System.Security.Cryptography.Xml * System.Threading.Tasks.DataFlow * Re-enable System.Net.Http.WinHttpHandler * System.Text.Json * Microsoft.Extensions.DependencyModel * System.Formats.Asn1
              
                    carlossanlop
  
              
              commented
              
                  
                    Jul 15, 2024 
                  
              
              
            
            
| <IncludeDllSafeSearchPathAttribute>true</IncludeDllSafeSearchPathAttribute> | ||
| <AllowUnsafeBlocks>true</AllowUnsafeBlocks> | ||
| <IsPackable>true</IsPackable> | ||
| <GeneratePackageOnBuild>true</GeneratePackageOnBuild> | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file was stayed enabled as we introduced another change this month.
              
                    vseanreesermsft
  
              
              approved these changes
              
                  
                    Jul 15, 2024 
                  
              
              
            
            
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
  This was referenced Jul 16, 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.