Clean up async timeout extension methods

[JamesNK]

There are async timeout extension methods available in Microsoft.AspNetCore.Testing, e.g. await task.TimeoutAfter().

Many ASP.NET Core projects have there own copies of these timeout methods, or wrap them in there own extension methods (probably done to remove a copy while minimizing changes), e.g. https://github.com/aspnet/AspNetCore/blob/master/src/Hosting/TestHost/test/Utilities.cs

We should go through aspnetcore/extensions and clean up the copies and wrappers.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[JunTaoLuo]

This seems like a simple clean up item but also seem like it's of low priority.

[davidfowl]

We should replace this with the new built in Task.WaitAsync methods.

[ladeak]

It is itchy to replace TimeoutAfter (including DefaultTimeout, OrTimeout, WithTimeout) extension methods, but some of them tend to create a custom timeout exception message using filePath, lineNumber.

[SuppressMessage("ApiDesign", "RS0026:Do not add multiple public overloads with optional parameters", Justification = "Required to maintain compatibility")]
private static async Task TimeoutAfter(this Task task, TimeSpan timeout,
    [CallerFilePath] string filePath = null,
    [CallerLineNumber] int lineNumber = default)

and message created as:

private static string CreateMessage(TimeSpan timeout, string filePath, int lineNumber)
            => string.IsNullOrEmpty(filePath)
            ? $"The operation timed out after reaching the limit of {timeout.TotalMilliseconds}ms."
            : $"The operation at {filePath}:{lineNumber} timed out after reaching the limit of {timeout.TotalMilliseconds}ms.";

The suggested WaitAsync does not seem to have an overload that takes a message parameter.

Can I remove this custom error message with the filePath and lineNumber, or they must stay?

[davidfowl]

Hmmm, good point. Maybe we keep the extension methods and replace to implementation and catch the error thrown by WaitAsync and rethrow our own.