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
One of our unit tests fails, because it looks like the BCL is broken. The first
DST transition is meant to be at 2012-01-01T00:00:00 local time (according to
the adjustment rule) but it appears to actually occur at 2012-01-01T00:00:00Z.
(In every other case, the adjustment rule is treated as being local time.)
Have filed a connect bug about it:
https://connect.microsoft.com/VisualStudio/feedback/details/787282/libyan-time-z
one-has-incorrect-initial-transition#details
We'll see what happens to it before deciding what to do in Noda Time.
Original issue reported on code.google.com by jonathan.skeet on 21 May 2013 at 1:36
The text was updated successfully, but these errors were encountered:
It's been acknowledged as a BCL bug, although with an odd comment which
suggests that the responder didn't quite understand what I'd said.
This only makes a difference for a single hour (in the past) in Libya, in a
time zone which I suspect doesn't bear much resemblance to reality anyway.
For the moment at least, I'm just suppressing that one transition in the tests.
Original comment by jonathan.skeet on 23 May 2013 at 3:35
Original issue reported on code.google.com by
jonathan.skeet
on 21 May 2013 at 1:36The text was updated successfully, but these errors were encountered: