A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.


Back in the 90’s I had to debug a printer routine in a reporting tool. It would occasionally crash. Only on Wednesdays. Only on Wednesdays in September. Only on Wednesdays in September after September 9th.
Code was written in c.
What was the fix. I’m a dumb data scientist, I don’t know C
c requires you to do things like define the maximum length of a string. In fact a string in c is literally defined as an array of characters. There are no protections in c, so you can define a string to be 10 characters long and then copy 20 characters to it. The result is most often a stack overflow that immediately crashes the program.
This was legacy code that was likely written in the early days of DOS before things like Microsoft Windows existed, so memory usage was still pretty important. Whoever wrote this code tried to calculate the maximum size of a string used to print a header in this reporting package as a way to optimize memory usage. But they were off by one character. So when the code created a header with a date containing the longest month name, the longest date name, and a two digit day of the month, then that string overflowed and crashed the program.
Might be the character count. Wednesday has many, September has many, after the 9th has two.
Program filling the date into a form field of width 1 less than was possible with actual dates.
this but string length according to OP.
As an even dumber data analyst, something about this comment makes me feel seen. Thank you. <3