Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So is this a feb 29 bug? Problem occurred, it seems, at the advent of 2/29 GMT. Worst date handling ever?


Apparently electronic payment systems from ATMs to merchant terminals to HMO claim machines all went straight to march 1st. Hilarity ensued.


Yeah, and I noticed my paycheck arrived a day early.


"We have identified the root cause of this incident. It has been traced back to a cert issue triggered on 2/29/2012 GMT"


It's a bit unfortunate description of time, I think. They could at least say "2/29/2012 01:45 GMT". Otherwise it looks like there's a different date in each timezone (yeah, there are two different ones, but not different in each, the bug started closer to beginning of 2/29/2012 GMT+2).


I think this is the problem with rewriting platforms, libraries and languages from scratch instead of incrementally chiseling it into something stable like in the open unix world.


instead of incrementally chiseling it into something stable like in the open unix world.

LOL. If I had a penny for whenever the "open unix world" chose to re implement some stuff from scratch, I'd be rich. From Gnome and KDE always changing stuff (especially the KDE multimedia architecture took this to comical levels), to FreeBSD moving to Clang...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: