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
Every year, between 1 AM and 2 AM local time (Eastern or America/New_York), our PHP project that uses this Duo universal client throws exceptions for all calls to healthCheck().
Expected Behavior
I expect the Duo client to handle a time change correctly ;-)
Actual Behavior
The universal client library appears to not handle the DST change correctly, for some reason.
Steps to Reproduce
This is probably not reproducible without waiting for the next DST change?
1.
2.
3.
4.
Workarounds
The problem resolves itself at 2 AM local time. We could also bypass the healthcheck() call between 1 AM and 2 AM, probably, as a workaround.
The text was updated successfully, but these errors were encountered:
Description
Every year, between 1 AM and 2 AM local time (Eastern or America/New_York), our PHP project that uses this Duo universal client throws exceptions for all calls to healthCheck().
Expected Behavior
I expect the Duo client to handle a time change correctly ;-)
Actual Behavior
The universal client library appears to not handle the DST change correctly, for some reason.
Steps to Reproduce
This is probably not reproducible without waiting for the next DST change?
1.
2.
3.
4.
Workarounds
The problem resolves itself at 2 AM local time. We could also bypass the healthcheck() call between 1 AM and 2 AM, probably, as a workaround.
The text was updated successfully, but these errors were encountered: