Question

使用超时和CancellationToken调用Async.RunSynchronously时，似乎忽略了超时值。我可以通过在CancellationToken上调用CancelAfter来解决这个问题，但理想情况下我希望能够区分工作流中出现的异常，TimeOutExceptions和OperationCanceledExceptions。

我相信下面的示例代码证明了这一点。

open System
open System.Threading

let work = 
    async {
        let endTime = DateTime.UtcNow.AddMilliseconds(100.0)
        while DateTime.UtcNow < endTime do
            do! Async.Sleep(10)
            Console.WriteLine "working..."
        raise ( Exception "worked for more than 100 millis" )
    }


[<EntryPoint>]
let main argv = 
    try
        Async.RunSynchronously(work, 50)
    with
        | e -> Console.WriteLine (e.GetType().Name + ": " + e.Message)

    let cts = new CancellationTokenSource()

    try
        Async.RunSynchronously(work, 50, cts.Token)
    with
        | e -> Console.WriteLine (e.GetType().Name + ": " + e.Message)  


    cts.CancelAfter(80)
    try
        Async.RunSynchronously(work, 50, cts.Token)
    with
        | e -> Console.WriteLine (e.GetType().Name + ": " + e.Message)  

    Console.ReadKey(true) |> ignore

    0

输出如下，表明超时仅在第一种情况下有效（未指定CancelationToken）

working...
working...
TimeoutException: The operation has timed out.
working...
working...
working...
working...
working...
working...
working...
Exception: worked for more than 100 millis
working...
working...
working...
working...
working...
working...
OperationCanceledException: The operation was canceled.

这是预期的行为吗？有没有办法得到我追求的行为？

谢谢！

Answer 1

我不确定这是否是预期的行为 - 至少，我认为没有任何理由。但是，此行为直接在RunSynchronously的参数处理中实现。如果您查看library source code，可以看到：

static member RunSynchronously (p:Async<'T>,?timeout,?cancellationToken) =
  let timeout,token =
    match cancellationToken with
    | None -> timeout,(!defaultCancellationTokenSource).Token                
    | Some token when not token.CanBeCanceled -> timeout, token                
    | Some token -> None, token

在您的情况下（同时具有可以取消的超时和取消令牌），代码将通过最后一个分支并忽略超时。我认为这可能是一个错误，也可能是文档中应该提到的。

作为一种变通方法，您可以创建单独的CancellationTokenSource来指定超时并将其链接到主取消源，以便调用者提供（使用CreateLinkedTokenSource）。当您获得OperationCancelledException时，您可以检测源是实际取消还是超时：

type Microsoft.FSharp.Control.Async with
  static member RunSynchronouslyEx(a:Async<'T>, timeout:int, cancellationToken) =
    // Create cancellation token that is cancelled after 'timeout'
    let timeoutCts = new CancellationTokenSource()
    timeoutCts.CancelAfter(timeout)

    // Create a combined token that is cancelled either when 
    // 'cancellationToken' is cancelled, or after a timeout
    let combinedCts = 
      CancellationTokenSource.CreateLinkedTokenSource
        (cancellationToken, timeoutCts.Token)

    // Run synchronously with the combined token
    try Async.RunSynchronously(a, cancellationToken = combinedCts.Token)
    with :? OperationCanceledException as e ->
      // If the timeout occurred, then we throw timeout exception instead
      if timeoutCts.IsCancellationRequested then
        raise (new System.TimeoutException())
      else reraise()

F＃Async.Run与timeout和cancellationToken同步

1 个答案: