* Flag tests being retried on Helix
This should make it easier to clean them up and also incidate to buildops engineers that failures warrant quarantine.
* Clean out helix retry list
Mark all flagged tests as `[Repeat(100)]` to get new failure data for quarantining.
* Quarantine LocationChangingHandlers_CannotCancelTheNavigationAsynchronously_UntilReturning
* Quarantine ChangingUserNameDuringReconnectLogsWarning
* Quarantine InjectedStartup_DefaultApplicationNameIsEntryAssembly
* Quarantine BidirectionalStream_ServerReadsDataAndCompletes_GracefullyClosed
* Quarantine ServerReset_BeforeRequestBody_ClientBodyThrows
* Quarantine ClientAbortingConnectionImmediatelyIsNotLoggedHigherThanDebug
* Quarantine CanLaunchPhotinoWebViewAndClickButton
* Quarantine HttpsConnectionClosedWhenResponseDoesNotSatisfyMinimumDataRate
* Add comments to test-configuration.json
* Support return operations using switch expressions
* Fix handling of allReturnStatementsReadable, localActualResponseMetadata
* Use collection expression
* Split up test files
These entries were missed in #48238. InvariantGlobalization should only be set when the template is created for native AOT. That is the way it is for the worker and grpc templates already. These templates don't support AOT.
Fix#52319
* 1. fix enhanced form handling use default enctype when not specified
2. fix enhanced form handling honor form enctype attribute
3. fix enhanced form handling honor submit button formenctype attribute
* use SupplyParameterFromQuery to provide enctype and formenctype in the tests
## Issue: Microsoft.AspNetCore.Components.WebView.props is not imported by Maui applications
This issue pertains to the fact that the Microsoft.AspNetCore.Components.WebView.props file is not being imported by Maui applications. The file has been relocated within the package to ensure its correct pickup and importation during the restore/build process.
Fixes#42348.
## Description
The inability of Maui applications to rely on JavaScript (JS) initializers, particularly in the case of Fluent UI, is impacted by this issue. The runtime searches for the initializer's definition in a specific location, which is configured in the props file of the package.
## Impact on Customers
The malfunction of JS initializers in Blazor Hybrid has significant implications for both library authors and end users.
Library authors may find their libraries' functionality restricted due to this bug. JS initializers, a feature in Blazor, enable library authors to inject scripts onto the page at the start of the app. These scripts can augment functionality, enhance user interfaces, or facilitate third-party service integration. For instance, a library author might employ a JS initializer to inject a script that integrates with a mapping service, thereby providing real-time location updates within a Blazor app. This functionality would be unavailable in Blazor Hybrid apps due to this bug.
End users may be unable to use certain libraries, or those libraries may not function as anticipated in Blazor Hybrid apps. If a user were to use a Blazor Hybrid app that relies on the aforementioned mapping library, they would not receive the real-time location updates that they would in a regular Blazor app. This could result in an inferior user experience, and in some cases, render the app unusable.
Users and library authors are compelled to manually inject the script onto the page, and some functionality (like configuring Blazor before it starts) is not available in this mode.
## Regression?
- [ ] Yes
- [X] No
## Risk
- [ ] High
- [ ] Medium
- [X] Low
The failure to load a file from a NuGet package impacts the build. The change causes the file to load at build time, enabling the rest of the pipeline to function as expected.
## Verification
- [X] Manual (required)
- [ ] Automated
The changes were made locally on the package cache and ensured the file got imported.
## Packaging changes reviewed?
- [ ] Yes
- [ ] No
- [x] N/A
## When servicing release/2.1
- [ ] Make necessary changes in eng/PatchConfig.props
* Remove unneeded unboxing/boxing
* Add doc comment
* Remove unused using
* Convert F# Async<> to Task<> in request delegates
* Use `CoercedAwaitableInfo` to convert `FSharp.Control.FSharpAsync<T>`
values to `System.Threading.Tasks.Task<TResult>` when building request
delegates and populate endpoint metadata accordingly.
* Add tests for F# async request delegate support
* F# async not supported by source generator
* Add a comment to the request delegate source generator tests that
explicitly calls out that F# async is not currently supported by the
source generator.
* Actually remove extra convert call
* Shrink diff
* Use CoercedAwaitableInfo in OpenApi gen
* Use CoercedAwaitableInfo in EndpointMetadataApiDescriptionProvider
* Add FSharpAsync tests for EndpointMetadataApiDescriptionProvider
* Add runtime creation test for FSharpAsync
* Convert unit awaitables to void awaitables
* FSharpAsync<unit> → Task
* Task<unit> → Task
* ValueTask<unit> → ValueTask
* Add tests for unit → void awaitable conversions
* Make consistent
* Don't need
* Handle boxed IResult
* Simplify
* Add runtime tests back
* Use affirmative form
---------
Co-authored-by: Safia Abdalla <safia@microsoft.com>
dotnet-maestro[bot]
Chary
Andrew Casey
Marc Gravell
Xavier Abelaira Rueda
Paulo Morgado
kirides
dependabot[bot]
James Newton-King
David Acker
Alireza Habibi
zori
Chris Ross
Mariusz Stępień
Eric Erhardt
Surayya Huseyn Zada
Javier Calvarro Nelson
Brian Rourke Boll
Sébastien Ros
Aleks Vujić