Leap Year Unplanned Feature?
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
-
Yep, Chris wrote that in a recent Code Project newsletter.
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
AspDotNetDev wrote:
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day).
I'd go for the second one because it doesn't expire until 2103. That's 91 years from now.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
AspDotNetDev wrote:
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day).
I'd go for the second one because it doesn't expire until 2103. That's 91 years from now.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Butterfingers. :)
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
Well, we had a funny that took up most of Tuesday. Any .Net DateTimePickers in a WinForm that had a custom date format that didn't show the day (e.g. just showing Month and Year - 'MM yyyy') caused an exception on trying to change the year. Internally, the control didn't change the day when changing the year from 2012 to 2011, causing a date of 29/02/2011. The DTP threw an exception. This affected 17 forms in 1 program. To get round it, on loading the form I made sure that the date was formatted to 01/ + whatever the current month and year are. :( Julian
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
Once upon a time I wrote control software for a device that had maintained its own date and time. My application set the date and time to match the controlling PC, for the sake of consistency. While we were testing this, we discovered that the device didn't let me set leap days: February 29th. I explained this to the yutz who wrote the firmware for the device, and he gave me a correction. Now the device wouldn't let me set dates in February at all. :rolleyes:
Software Zen:
delete this; -
Well, we had a funny that took up most of Tuesday. Any .Net DateTimePickers in a WinForm that had a custom date format that didn't show the day (e.g. just showing Month and Year - 'MM yyyy') caused an exception on trying to change the year. Internally, the control didn't change the day when changing the year from 2012 to 2011, causing a date of 29/02/2011. The DTP threw an exception. This affected 17 forms in 1 program. To get round it, on loading the form I made sure that the date was formatted to 01/ + whatever the current month and year are. :( Julian
That's what you get for using the "Julian" calendar. ;)
-
That's what you get for using the "Julian" calendar. ;)
Very funny.... :laugh: And I meant Wednesday in my post not Tuesday BTW. J
-
Well, we had a funny that took up most of Tuesday. Any .Net DateTimePickers in a WinForm that had a custom date format that didn't show the day (e.g. just showing Month and Year - 'MM yyyy') caused an exception on trying to change the year. Internally, the control didn't change the day when changing the year from 2012 to 2011, causing a date of 29/02/2011. The DTP threw an exception. This affected 17 forms in 1 program. To get round it, on loading the form I made sure that the date was formatted to 01/ + whatever the current month and year are. :( Julian
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
What time was this? (In UTC time. In your local time. The local time of the registering authority?) You add a year or 365 days in SQL on a Feb 29 date, it is Feb. 28. You add a year or 365 days on Feb 28th in a leap year, you get Feb 28 OR Feb 27. It's 4PM here now, so we just turned to a new day on UTC time.
-
I registered a couple domains today at the same time (part of the same order) and I got an email that states when they expire. One expires on February 28th, 2013 and the other on March 1st, 2103. Leap year bug? Or maybe it's a "feature" (they randomly choose one of the two adjacent days for the expiration of domains registered on a leap day). :-D
In our software we had a verification if the person is older than 18 years That went wrong on 29th February, because someone just did this: Today() -18 years The date was invalid then and the verification said the person is under 18 years although it was older than 18 years old.
