look at the Core 0 graph
So are we just ignoring core 1 orrrrr
Welcome to /c/SoftwareGore!
This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!
Remember to read the rules before you make a post or comment!
Community Rules - Click to expand
These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)
You should also check out these awesome communities!
look at the Core 0 graph
So are we just ignoring core 1 orrrrr
Ahh, didn't notice that
OP witnessed the leap second
Yo, how did you get your computer to time travel? 🥸
NTP time synchronization. The computer's real-time clock was ahead of the actual time, and Windows updated it to the correct time.
Why would the software developer(s) use the time instead of a timer to make a graph?
It's possible they did both.
If that graph widget is designed for time-series data, it would need an X-axis timestamp and corresponding Y-axis value for every different sensor it renders. A timer would be used to periodically take samples, and the sample would be created with a timestamp of whenever the timer fired.
Users usually don't want to see a monotonic time on the X axis, they want to see wall time.
Must be the choice of steins;gate
Behold the divergence number!
A prime example of why one should use the monotonic clock.
Jump in loser, we're going time traveling!
Carl, we told you not to divide by 0 again!
bro where did you get a quantum computer!?