Ours did.

Bad date processing fails badly.

Truth. Our problem stems from a calculation which tries to get the date a year from now. The developer thought it would be safe to just get the current day, month and year add construct a new date after adding 1 to the year.

Fail :(

Our phone system is completely dead- internal and external. Not ideal. We didn't even write that! 

 On a similar note...

Feb 29 broke our software early; in the first week of January. It's supposed to do some calculations with the longest running contracts for a customer. This particular customer had a couple of short contracts and two full year contracts; 2007 and 2008. Yet our software only picked 2008 and seemed to ignore the 2007 contract. It turned out, of course, that the length of the contract was calculated in days, which made the 2008 contract slightly longer that the 2007 one.

 Minor problem with one test system here. A table is supposed to contain one entry per day, but on the test system, my coworker just copied last year's data. Of course today's entry is missing. Of course exactly today we had a meeting with a customer and showed him the application.

I'm running PointUI (www.pointui.com) on an iPaq. Today, it decided that it was 12:00AM 1/1/1601 until I quit the app, then it completely refused to run until I set the date back to yesterday.

Ours is fine here, but a few of my colleagues had problems with their contactless payment cards for the trams on the way to work - they let you 'tag on' but gave an invalid date error on tagging off. Meaning you got charged as if you went from one terminus of the line to another.

www.luas.ie being the offenders ehre. 

Ah, leap day... when CmpDates() returns 0 for CmpDates(2292008, 3012008).

Well, actually, CmpDates() would return 0 in that case anyway...

(And yes, CmpDates() and our date representation are WTFs.)

MetalPig:

Feb 29 broke our software early; in the first week of January.

Same here. A routine for calculating the first (part-month) payment on a new mortgage was failing for January - but not February - of a leap year. The method involves subtracting months and then subtracting days, (including an extra day to ignore Feb 29). Trouble is, Feb 29 might already have been skipped by the subtract-months part, making the result one day short of what it should be.

The code's been like that for well over 4 years. Seems no-one spotted the problem in January 2004.

The real WTF is the number of different calculation options for this routine - or maybe it's when one of our users queries the calculation because they've been given some simple documentation from 9 years ago that no longer matches the way it works.

 Ours did, although I have a feeling it was human error last night rather than computer error this morning. ("28th Feb? Oooh monthend! Best run all those processes!") 

Not a tech WTF but here goes.

I signed the lease for my apartment February 1, 2007.  It was a 13 month lease, ending on Feb 28, 2008.

I signed a new lease in January.  It'a 13 month lease going from March 1, 2008 to March 31, 2009.  

Today, they have no contractual obligation to let me stay there.  I also have no contractual obligation to pay to live there today. 

Since they're not kicking me out, I get a day for free*! 

free = not free 

 Is that all?

 Keep 'em coming!

 I don't have anything.

Everything works. 

Mine didn't break, but somebody else in the company did.  They were using a SimpleDateFormatter to parse a date in "MM/DD" format without considering the year.....

The email bounced around through several layers of management before wwasting an hour of my time checking our code.  I did, however find a similar bug in the CSWDateTime class which....basically does the same stuff java.util.Date does, only in a halfassed way....

    public static long calcWaitMillis(String endDateTime) {
        Date endDate = getDate(endDateTime);
        return endDate.getTime() - new Date().getTime();
    }

    public static Date getDate(String dateTime) {
        SimpleDateFormat dateFormatter = null;
        if (dateTime.length() > 8) {
                // assume a date-time has been passed in
            dateFormatter = new SimpleDateFormat("yyyyMMdd HH:mm:ss");
        }
        else {
            // just a time has been passed in
            dateFormatter = new SimpleDateFormat("HH:mm:ss");
        }

        ParsePosition pp = new ParsePosition(0);
        Date date = dateFormatter.parse(dateTime, pp);
            // date should correspond to 1st Jan 1970 hh:mm:ss
        if (date == null) {
            date = new Date(0); // 1st Jan 1970 00:00:00
            Trace.log(1, "Invalid date <" + dateTime + ">, setting to " +
                      date.getTime());
        }
        return date;
    }

 Good thing nobody actually uses it....

 *ding*

 As an added bonus, since it's a Friday, and we don't normally run production operations on a Friday unless we're behind schedule, nobody would have noticed for another four years.

belgariontheking:

I signed the lease for my apartment February 1, 2007.  It was a 13 month lease, ending on Feb 28, 2008.

I signed a new lease in January.  It'a 13 month lease going from March 1, 2008 to March 31, 2009.

My lease on my old apartment started December 15th, 2006, and ended on December 15th 2005.  I saw the error but signed it anyhow, just incase.  As luck would have it, I had to move out of town mid-2006.  Good thing I wasn't contractually obligated to keep paying rent or pay the "early termination" fee.

belgariontheking:

Not a tech WTF but here goes.

I signed the lease for my apartment February 1, 2007.  It was a 13 month lease, ending on Feb 28, 2008.

I signed a new lease in January.  It'a 13 month lease going from March 1, 2008 to March 31, 2009.  

Today, they have no contractual obligation to let me stay there.  I also have no contractual obligation to pay to live there today. 

Since they're not kicking me out, I get a day for free*! 

free = not free 

Kinda ironic how the guy who keeps saying I'm 12 years old still rents while I have a mortgage. *snicker* 

Maybe that's just the apartment he uses to keep his wife from finding out about his mistress.

P.S. If you have an adjustable rate mortgage, you're really not making a good case for yourself.

Lysis:

Kinda ironic how the guy who keeps saying I'm 12 years old still rents while I have a mortgage. *snicker* 

Yeah, but his rent is on an actual apartment, while your "mortgage" is what you pay the other bums under the bridge to stay away from your box.

Back to /., script kiddie, and let the grownups talk. 

vt_mruhlin:

Maybe that's just the apartment he uses to keep his wife from finding out about his mistress.

P.S. If you have an adjustable rate mortgage, you're really not making a good case for yourself.

Uhhh no. Just no. 

Squiggle:

Ours did.

Bad date processing fails badly.

You knew about the three year life cycle in 2004 when you guys wrote it. You need to work on your AutoObsolete functionality. 

medialint:

Squiggle:

Ours did.

Bad date processing fails badly.

 

You knew about the three year life cycle in 2004 when you guys wrote it. You need to work on your AutoObsolete functionality. 

We were since bought out by a company that expected our product to actually work.

On a similar note, today has been SO MUCH FAIL:

• The live software broke due to a leap year bug.
  
• The coffee machine broke
• The Internet was down for half the day (a city-wide outage for one of the main ISPs)
  
• I got rained on at lunchtime and now I have a very soggy left foot
• The project we've been working on for the past 9 months just got cancelled (technically "put on hold", but we all know how that pans out...).

Wonderful.

I need a beer.

Squiggle:

The Internet was down for half the day

Oh crap! When was someone going to tell me the tubez were broken???

Wait... What?