You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this is expected behaviour, it should be explained in detail in the docs. It currently only says "Query timeout" which is pretty vague. I expected this to be a timeout for any method (async or synchronous) that I call on the NtpClient method (and not on the underlying socket). I think the timeout should be implemented differently, perhaps using a CancellationTokenSource and CancelAfter
The text was updated successfully, but these errors were encountered:
I'm doing this as a workaround which seems to work.
var client = new NtpClient(...);
var cts = new CancellationTokenSource();
cts.CancelAfter(TimeSpan.FromSeconds(1));
await client.QueryAsync(cts.Token);
Tested with GuerillaNtp v3.0.0 & .NET for macOS
Code:
Expected behaviour:
OperationCanceledException
or similar ExceptionActual behaviour:
Timeout is ignored.
QueryAsync
can be awaited for much longer, potentially indefinitely, without any exception being thrown.The docs only mention that the synchronous Receive method might use this timeout.
https://learn.microsoft.com/en-us/dotnet/api/system.net.sockets.socket.receivetimeout?view=net-7.0
There's also another Timeout, for synchronous Send methods, currently it doesn't seem to be used anywhere in this library: https://learn.microsoft.com/en-us/dotnet/api/system.net.sockets.socket.sendtimeout?view=net-7.0
If this is expected behaviour, it should be explained in detail in the docs. It currently only says "Query timeout" which is pretty vague. I expected this to be a timeout for any method (async or synchronous) that I call on the NtpClient method (and not on the underlying socket). I think the timeout should be implemented differently, perhaps using a
CancellationTokenSource
andCancelAfter
The text was updated successfully, but these errors were encountered: