Board index » "Sep 30" rustypod commit - did anyone actually CONVERT the timestamp to UTC before calling it a frame shift :rolleyes:

FlameFury24
Inner Circle
★★★★★
Cheese Receipt TruthSakuraBanned147witnessDoubleZeroPusher
Posts: 2495
Reputation: +3 ■
Joined: May 15, 2006
From: The Inferno Pit, USA
So s2pid_rox and Lyrik caught the locale change from dd-mmm-yyyy to "Sep 30" in the rustypod commit log - great, good job, pat on the back :dumbbravo: but did ANYONE bother to check what timezone the server is actually reporting from?? It's 2AM Eastern right now which means UTC is still Sep 29. If the commit says "Sep 30" at UTC-4 it's a future-dated commit by like 6+ hours, not a locale shift. That's a CLOCK DRIFT, not a locale config. Lyrik's split terminal screenshot is solid methodology but the timestamp math is incomplete :rolleyes: TechAngel you're the one who corrected the day count yesterday - get in here and check if the epoch time on that commit is ahead of the actual wall clock :confused: CommitCipher's two-server theory holds up BETTER if the timestamp is pre-dated because that means someone pushed from a box with a wrong system clock, not just en_US locale. And if the clock is wrong, check the key age against the server's idea of what year it is :D :D :P

Oh and prairie_pilgrim wrote four paragraphs about a classical guitar hanging on a fence post like it's the Shroud of Turin and not a yard sale prop from CornfieldCrazy_82's uncle's barn :rofl: liturgical silence my ass, the strings are SLACK - that guitar hasn't been tuned since Bush was in his first term :spitfire: :spitfire: but that's a thread for another board :backtotopic:

"See you there." - someone who actually means it. Day 11 of TwinPeaks' overdue WAV. Get rekt.