-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SntpClient failure notification #12
Comments
The actual reason for the failure isn't that interesting. It can be a network cable not connected, bad WIFI connection,etc. We want to handle all errors in the same manner |
I think that the problem is that MaybeOperationTimeout is not checking to see if a socket was created:
This results in an unnecessary retry because Dns.BeginGetHostAddresses is failing (it takes longer than 1/2 second) and there is no socket. |
The problem is that it is notifying the failure multiple times. I think I think that the root cause of the problem that MaybeOperationTimeout is What I did was:
Thanks for contributing the code. On Thu, Aug 27, 2015 at 12:18 AM, Ayende Rahien [email protected]
|
Can you show your changes? I'm not sure that I can follow from the description. |
See attached code. On Fri, Aug 28, 2015 at 5:53 AM, Ayende Rahien [email protected]
using System; namespace LicensingShared
} |
I can't really read this. Can you send this as a PR, that way it would be *Hibernating Rhinos Ltd * Oren Eini* l CEO l *Mobile: + 972-52-548-6969 Office: +972-4-622-7811 *l *Fax: +972-153-4-622-7811 On Fri, Aug 28, 2015 at 4:54 PM, trailway [email protected] wrote:
|
Done. My first pull request. On Fri, Aug 28, 2015 at 11:07 AM, Ayende Rahien [email protected]
|
Thanks, I mreged it. *Hibernating Rhinos Ltd * Oren Eini* l CEO l *Mobile: + 972-52-548-6969 Office: +972-4-622-7811 *l *Fax: +972-153-4-622-7811 On Fri, Aug 28, 2015 at 8:46 PM, trailway [email protected] wrote:
|
The SntpClient class is notifying failures multiple times. This can be reproduced by pulling the network cable from machine. I added the following check to avoid this:
I suspect that there may be a deeper problem here but the fix isn't obvious to me.
The text was updated successfully, but these errors were encountered: