Merging internal commits for release/8.0 #54011
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
…otnet-efcore build 20240110.10 dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer , Microsoft.EntityFrameworkCore.Tools From Version 8.0.2 -> To Version 8.0.2
…ng/internal/dotnet-efcore This pull request updates the following dependencies [marker]: <> (Begin:e179a2a7-bc5d-4498-2467-08dbd53ba9ce) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-efcore - **Subscription**: e179a2a7-bc5d-4498-2467-08dbd53ba9ce - **Build**: 20240110.10 - **Date Produced**: January 10, 2024 7:11:25 PM UTC - **Commit**: 1c9152ea533a90226306519f9c22e23add6b932c - **Branch**: refs/heads/internal/release/8.0 [DependencyUpdate]: <> (Begin) - **Updates**: - **dotnet-ef**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.Design**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.InMemory**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.Relational**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.Sqlite**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.SqlServer**: [from 8.0.2 to 8.0.2][1] - **Microsoft.EntityFrameworkCore.Tools**: [from 8.0.2 to 8.0.2][1] [1]: https://dev.azure.com/dnceng/internal/_git/dotnet-efcore/branches?baseVersion=GC856a15f40b4f27ab0f996e044b68943b9a9c75c0&targetVersion=GC1c9152ea533a90226306519f9c22e23add6b932c&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:e179a2a7-bc5d-4498-2467-08dbd53ba9ce)
Merge from public release/8.0 to internal/release/8.0 and resolve conflicts if necessary
We converted UtcNow.Ticks usage to Environment.TickCount64 usage. TickCount64 is in milliseconds and UtcNow.Ticks is in the 100-nanosecond scale. When we made this change we didn't convert TickCount64 to the same scale so comparisons were wrong.
…t-efcore, dnceng/internal/dotnet-runtime
# Auto render mode improvements Backport of dotnet#53159 Improves the Auto render mode so that components are more responsive and have a decreased initial time to interactivity when WebAssembly resources are not already cached. ## Description One of the goals of the Auto render mode was to allow apps to become interactive as quickly as possible via Server interactivity, while WebAssembly bits were downloaded in the background for use on future visits to the site. However, since WebAssembly resources were being downloaded with maximal parallelism, the quality of the websocket connection required for Server interactivity was negatively impacted, often to the extent that the websocket wouldn't connect until WebAssembly resources had finished downloading completely, largely defeating the purpose of the Auto render mode. This PR makes the following improvements: * Removes a problematic timeout on loading the WebAssembly boot config. This fixes a problem where Server interactivity was always being used when the boot config took too long to load. * Introduces a limit to the maximum parallel WebAssembly resource downloads when an Auto component initiates the startup of the WebAssembly runtime. This limit is set to 1 and overrides any user-specified limit. * Fixes an issue where the circuit sometimes remains open even if WebAssembly gets selected for Auto interactivity. I provided a preview of these changes in dotnet#52154 (comment) so that customers could try them out, and the feedback so far has been very positive. Fixes dotnet#52154 ## Customer Impact A significant number of customers reported being affected by this problem in issues like dotnet#52154. I supplied customers with a preview of the fix that they could patch it into their app, and many indicated that their problems were resolved by the fix. The Auto render mode was one of the key features released in .NET 8, so it's important that it works in the way we've been advertising. ## Regression? - [ ] Yes - [X] No ## Risk - [ ] High - [ ] Medium - [X] Low The core Auto render mode functionality is unaffected by this change - we added small tweaks to adjust the throttling amount and remove a problematic timeout. Additional tests were added to verify the changes in behavior, and we've been testing these changes manually to ensure they work well in real-world scenarios (various device types and connection qualities). ## Verification - [X] Manual (required) - [X] Automated ## Packaging changes reviewed? - [ ] Yes - [ ] No - [X] N/A
…ng/internal/dotnet-efcore This pull request updates the following dependencies [marker]: <> (Begin:e179a2a7-bc5d-4498-2467-08dbd53ba9ce) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-efcore - **Subscription**: e179a2a7-bc5d-4498-2467-08dbd53ba9ce - **Build**: 20240116.13 - **Date Produced**: January 16, 2024 5:25:41 PM UTC - **Commit**: 813b3f77e6761ae5f931d0581e9f43428538a6aa - **Branch**: refs/heads/internal/release/8.0 [DependencyUpdate]: <> (Begin) - **Updates**: - **dotnet-ef**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.Design**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.InMemory**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.Relational**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.Sqlite**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.SqlServer**: [from 8.0.2 to 8.0.2][3] - **Microsoft.EntityFrameworkCore.Tools**: [from 8.0.2 to 8.0.2][3] [3]: https://dev.azure.com/dnceng/internal/_git/dotnet-efcore/branches?baseVersion=GCe6ea1d746b32c71b700a1c89891ff5b390f7b36b&targetVersion=GC813b3f77e6761ae5f931d0581e9f43428538a6aa&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:e179a2a7-bc5d-4498-2467-08dbd53ba9ce)
…-merge-8.0-2024-02-13-1023
vseanreesermsft
requested review from
BrennanConroy,
halter73,
a team and
wtgodbe
as code owners
dotnet-issue-labeler
bot
added
the
area-infrastructure
Closed
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.