Twitter | Pretraživanje | |
to kubectl or not to kubectl that is the question 29. sij
Odgovor korisniku/ci @mgattozzi
Reply Retweet Označi sa "sviđa mi se"
Geoffroy Couprie 29. sij
Odgovor korisniku/ci @mgattozzi
Oh no I had completely forgotten about this and it is the most cursed thing. Can't even trust time
Reply Retweet Označi sa "sviđa mi se"
to kubectl or not to kubectl that is the question 29. sij
Odgovor korisniku/ci @gcouprie
Trust no one, not even yourself
Reply Retweet Označi sa "sviđa mi se"
iximeow 29. sij
Odgovor korisniku/ci @mgattozzi
following up on the relevant linux bugs is fun:
Reply Retweet Označi sa "sviđa mi se"
to kubectl or not to kubectl that is the question 29. sij
Odgovor korisniku/ci @iximeow
Excuse me
Reply Retweet Označi sa "sviđa mi se"
NickH 29. sij
Odgovor korisniku/ci @mgattozzi @lukechampine
you'll love this
Reply Retweet Označi sa "sviđa mi se"
Luke Champine 29. sij
Odgovor korisniku/ci @NickHansen600 @mgattozzi
Oof. I wonder how Go handles it...
Reply Retweet Označi sa "sviđa mi se"
Tensibai 29. sij
Odgovor korisniku/ci @mgattozzi @DenysSeguret
May be dumb, BUT could it be related to systems using ntp under virtualization? The problem was widely known at a time before VMware add the sync clock to host as ntp was correcting too much when the cpu got the missing ticks from suspension
Reply Retweet Označi sa "sviđa mi se"
to kubectl or not to kubectl that is the question 29. sij
Odgovor korisniku/ci @Tensibai @DenysSeguret
It's not ntp. It has to do with clocks in things like the CPU and how the os gets them and interprets it.
Reply Retweet Označi sa "sviđa mi se"
Wesley Wiser 29. sij
Odgovor korisniku/ci @mgattozzi
The prior version of this code wasn't so comprehensive and I broke some people's rustc by relying on this being monotonic 😬
Reply Retweet Označi sa "sviđa mi se"
Wesley Wiser 29. sij
Odgovor korisniku/ci @mgattozzi
So if you want proof this happens not just in theory, there's all the duplicate issues.
Reply Retweet Označi sa "sviđa mi se"