Post Ak4HD2TVacYC2nLCRU by tillmanreuter@ecoevo.social
(DIR) More posts by tillmanreuter@ecoevo.social
(DIR) Post #Ak4AY9AFDNfBC0Rqsq by foone@digipres.club
2024-07-18T20:35:30Z
0 likes, 0 repeats
Imagine your software develops a bug of the same sort as that OpenOffice bug where you can't print on Tuesday: How long does it take you to figure out that the random intermittent failures aren't random at all, and are actually based on the day of the week?
(DIR) Post #Ak4AkGV7lLb1QEzdC4 by foone@digipres.club
2024-07-18T20:37:35Z
0 likes, 0 repeats
(it was actually a bug in gnu file that misidentified postscript files as erlang files if they had "Tue" in the right position, which caused cups to not print them)
(DIR) Post #Ak4B06E3jXQuBgYrvk by foone@digipres.club
2024-07-18T20:39:55Z
0 likes, 0 repeats
the openoffice bug was reported in july of 2008 and no one figured out the tuesday connection until april of 2009
(DIR) Post #Ak4BD6erRBmbIDIebg by mhoye@mastodon.social
2024-07-18T20:42:17Z
0 likes, 0 repeats
@foone It's right up there with "I can't send email more than 500 miles" story, for sure.
(DIR) Post #Ak4BRSpFocv26B0WMy by foone@digipres.club
2024-07-18T20:44:01Z
0 likes, 0 repeats
@obfusk whoops. misremembered. thanks for catching that!
(DIR) Post #Ak4BYUhBGJWZvOaEJk by albertcardona@mathstodon.xyz
2024-07-18T20:44:37Z
0 likes, 0 repeats
@foone That's up there with the 500-mile email!https://www.ibiblio.org/harris/500milemail.html
(DIR) Post #Ak4BhKcs4NgnIimWgK by foone@digipres.club
2024-07-18T20:47:37Z
0 likes, 0 repeats
though I imagine that process took longer than it should have because it was a printing bug. of course sometimes printing doesn't work. that's how printers ALWAYS act.
(DIR) Post #Ak4CaAdotUfWGFNICO by EndlessMason@hachyderm.io
2024-07-18T20:57:14Z
0 likes, 0 repeats
@foone1. git grep rand2. Tell reporter the printing code isn't random
(DIR) Post #Ak4DsJmpjLN5n8o9cO by fgrosshans@mathstodon.xyz
2024-07-18T21:12:21Z
0 likes, 0 repeats
@foone The original bug is here https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161 . No one understands the bug at all for a long time, until the wife of a developer is hit by the bug, identifies it correctly, and demonstrate it to her (presumably skeptical) husband.(The actual fix is in https://bugs.launchpad.net/ubuntu/jaunty/+source/file/+bug/248619 , but it is less interesting to read)
(DIR) Post #Ak4E0BAPf6bFNIaMU4 by nev@bananachips.club
2024-07-18T21:13:28Z
0 likes, 0 repeats
@foone source for the above, if anyone didn't know: https://beza1e1.tuxen.de/lore/print_on_tuesday.html
(DIR) Post #Ak4EDiqFlraTa1c7gO by lukeshu@fosstodon.org
2024-07-18T21:14:34Z
0 likes, 0 repeats
@foone It wasn't day-of-the-week, but:Empirically, about 14 months; October of 2013 until January of 2015.https://labs.parabola.nu/issues/435
(DIR) Post #Ak4GE4JC9qI64BRaZU by zero@retroverse.social
2024-07-18T21:32:44Z
0 likes, 0 repeats
@foone Debugging print drivers is what we call a "target-rich environment".
(DIR) Post #Ak4HD2TVacYC2nLCRU by tillmanreuter@ecoevo.social
2024-07-18T21:44:22Z
0 likes, 0 repeats
@foone because every bug has a reason, it has a pattern. Let's hope we all never get something this farfetched
(DIR) Post #Ak4HZrohNnGjeH8bQG by hp@mastodon.tmm.cx
2024-07-18T21:53:21Z
0 likes, 0 repeats
@foone once again showing that computers were, in fact, a mistake! 😄
(DIR) Post #Ak4InafU2OaITHw2O8 by PJ_Evans@mas.to
2024-07-18T22:07:55Z
0 likes, 0 repeats
@foone Oh, like the legendary "phase of the moon" error!
(DIR) Post #Ak4J9UbtF2bs3OhLKC by foone@digipres.club
2024-07-18T22:11:42Z
0 likes, 0 repeats
@hp hey, it wasn't completely a mistake:https://digipres.club/@foone/112798824066210468
(DIR) Post #Ak4JQlUTjY3DKYT2xs by hp@mastodon.tmm.cx
2024-07-18T22:14:01Z
0 likes, 0 repeats
@foone you've changed my mind! 😄
(DIR) Post #Ak4LsezbgbMpC6SNOK by atrus@toot.cafe
2024-07-18T22:42:35Z
0 likes, 0 repeats
@foone having spent a little while in the SRE space, and having excellent logs visualizable in kibana, that's the sort of pattern where a weekday-type bug might show up a bit quicker. But it's a matter of having all the usage and error logs aggregated in one place. It kind of makes me want to say "yes" to more of those "would you share usage data" opt-in prompts. 🫤
(DIR) Post #Ak4MJ5x84WFaL2u2a0 by xpi@mastodon.social
2024-07-18T22:47:14Z
0 likes, 0 repeats
@foone libmagic is wild. Not always correct - but very entertaining.
(DIR) Post #Ak4bDffRs31cgHVLaS by Ertain@mast.linuxgamecast.com
2024-07-19T01:34:01Z
0 likes, 0 repeats
@foone They figured it out on a Wednesday, didn't they?
(DIR) Post #Ak4ekgOcTyy4ML495s by gnomon@mastodon.social
2024-07-19T02:14:03Z
0 likes, 0 repeats
@foone if I recall correctly ( @oration please fact check me here) ot took me just under a year to notice a sawtooth performance problem in the morning financial positions ingestion job at $PREVIOUS_EMPLOYER, then an hour to notice the period was ten _calendar_ days, then a week to track down that someone had written `chop` in a Perl script somewhere when they should have written `chomp`. (I didn't know Perl then and I still don't know.)
(DIR) Post #Ak52STa7mlEuIsIZ7o by vl2m@mastodon.gamedev.place
2024-07-19T06:39:36Z
0 likes, 0 repeats
@foone bugs like this are funny. I remember seeing a screenshot of a Steam forum page where someone complained about a bug about the trees. The solution was to set the date of the computer to 2012.
(DIR) Post #Ak5oqZnd7BYKKzAnHU by jes5199@mastodon.social
2024-07-19T15:32:59Z
0 likes, 0 repeats
@foone did I tell you about the app I shipped once that wouldn’t accept credit cards that expired in August or September
(DIR) Post #Ak61me8cLDqe2TRiyG by foone@digipres.club
2024-07-19T18:04:48Z
0 likes, 0 repeats
@eon gah, zebra. I used to use a zebra printer that would corrupt the labels if you moved the mouse "too much" while printing