It has been 0 days since I showed coworkers the cursed Instant::now() code from Rust stdlibpic.twitter.com/V5Rdzw0kDi
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
It's not ntp. It has to do with clocks in things like the CPU and how the os gets them and interprets it.
Yep, due to ntp basing the correction by fraction of difference per tick, when the machine gets 1k ticks suddenly ntp has not corrected the fraction and the time slide too far in the future and too far back after on heavy conditions. I saw it happen on time series DB with a ~
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.