As luck would have it, a change in the orchestration of the scripts that ran in this environment had been pushed the day before. This was believed to be the culprit. Engineering rolled things back to the previous release. Unfortunately, this made the problem worse.
-
-
Which, for absolute certain, you will be.
-
Undoubtedly. But hopefully we can minimize them to a background-radiation level.
- Još 1 odgovor
Novi razgovor -
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
+1. I've seen a bunch of invalid certificates being given out starting on January 19th 2013 with a (then typical) 25 year lifetime. We're already overdue for a bunch of fixes.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Fantastic thread and having worked on Y2K I know 2038 will be a much larger problem. Especially when testing and someone puts the date forward "just to test" and completely screws the database.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I think I missed what the cause was. Something related to dates, sure. But what was the actual problem and fix?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Nice thread but we need closure, what was the specific root cause so we can all not fall into the same trap?
-
32bit time_t wraparound, given the context, yeah?
Kraj razgovora
Novi razgovor -
-
-
@AbeGong new sales pitch haha -
Wow. This is a perfect Pipeline Debt Vignette, written like an investigative journalism piece contending for the pulitzer.
@expectgreatdata
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
:

