Look before you leap
-
Another 29th February issue: http://blogs.msdn.com/b/windowsazure/archive/2012/03/01/windows-azure-service-disruption-update.aspx
-
Whenever you click on the page, even in a dead spot, there's a short burst of loading. I assume this is their metrics system tracking what users do?
In any case, I said hello and gave them a smiley face.
-
@nexekho said:
Whenever you click on the page, even in a dead spot, there's a short burst of loading. I assume this is their metrics system tracking what users do?
It sends the url to sniff.visitstat.com , along with the metrics click coordinates and document dimensions.
-
When the page opened I got a message that said "The target of the callback could not be found", then it set focus to another MSDN window I already had open in a tab...that's some great coding right there.
-
Dear God, this means they are doing their own date manipulations? Why??
-
Either they're Time Lords, or someone divided by zero.
-
MS developers working on an MS system that supports MS hosted services and they don't trust thier MS created date-time libraries? That is taking not-created-here to a whole new level
-
There's an update: http://blogs.msdn.com/b/windowsazure/archive/2012/03/09/summary-of-windows-azure-service-disruption-on-feb-29th-2012.aspx
The bug specifically was in generating certificates and setting the end date by taking the current date and adding one to the year. A classic mistake - we just had a TDWTF about this very error on, of course, 29 February - and the sort of thing that makes you wonder who they're letting write critical infrastructure code for their much-hyped PaaS cloud offering.
And, as pointed out by others previously in this thread, it would have been simpler to use their own framework date class, which does one-year-in-the-future trivially.