WED Dec 31?? Really??

[SCW-Greg]

Well...
Happy (correct) New Year!

 

[scaesare]

They are converting from an internal representation based on metric time.

Yes, that's a joke.

 

[AudubonB]

An easy fix, Doc told me years ago (or was it in the future?).

Anyway, take a deadblow hammer and, between the nodes, give the flux capacitor two sharp raps. Re-sets the whole shebang.

 

[AnOutsider]

Now we know why all their product timelines are so screwed up.

 

[dsmith2189]

Yeah, Dec 31st is Wednesday in 2014.

And it is already Wednesday, 2014 (but Jan 1) accross the dateline in places like Australia.
The logic to figure out the day of the week must be 'goofy'. Maybe some sort of universal time translation bug going between date and day.

By the way, I had run into a 'bug' 14 years ago, when trying to one-click record the year 2000 new years eve fireworks show on my Tivo. It tried to go back and record the bit of 'buffer' from the previous year and ended up crashing and rebooting the unit instead of recording the show.

I was thinking it was because of a time zone calculation.
If they calculate the day of the week based on UTC and you are in a "-" time zone (the US) then your day of week will be calculated using the UTC Year instead of the time zone year

 

[Mayhemm]

Heh, remember how many years the iPhone has had similar time/date issues.

Yes, and apparently Tesla has now hired the person responsible. :tongue:

 

[yobigd20]

Just another example of the amateur software engineers at Tesla who don't thoroughly range bound test their code.

 

[dave]

Imagine if we all had our Teslas prior to the Y2K fiasco...

 

[widodh]

I had my car saying "Thursday January 1" and today it's saying "Thursday January 2".

 

[mitch672]

I had my car saying "Thursday January 1" and today it's saying "Thursday January 2".

Groundhog Day, everyday is Thursday