4 ms·

Ask HN: What bug did you finally fix and how? (success stories):)

2 points by logicallee 3y ago

I'd like to hear some of your longest stories of bugs that were hard to fix but that you finally ended up fixing in the end! I want to hear your success stories! :) How did you finally fix it?

aastronaut 3y ago
Fixed a bug on how the browser wasn't closing TCP connections/Motion JPEG video streams properly in a responsive behavior. Took me about 3+ hours reading through various specs and that resulted to around 20 LOC changed. I then wrote a blog post about it[0], which took me about 10 days. [0]: https://blog.whilenot.dev/posts/cool-bugs-vs-shitty-bugs-part-1/ https://blog.whilenot.dev/posts/cool-bugs-vs-shitty-bugs-par...
tlesko 3y ago
I remember the first time I wanted to install Android Studio. The problem was that the name of my user in Windows had an accent, and for some reason it wasn't installed correctly (I don't remember it that well, it was a long time ago). What I did was just changing the user name. The problem with this is that i tried a lot more that just this, I hand't except this could be the problem.
acemarke 3y ago
I wrote up several debugging stories on my blog a while back: https://blog.isquaredsoftware.com/2019/01/blogged-answers-debugging-tips/#tales-of-debugging https://blog.isquaredsoftware.com/2019/01/blogged-answers-de... (I think the "6 hours to change the case of 1 letter in a filename" is still the most amusing one!)
reliefcrew 3y ago
There are many, of course, but this one is somewhat recent. The story isn't long but finding/fixing it was certainly infuriating. For some reason xenial's nut-server package is missing "/lib/systemd/system-shutdown/nutshutdown" I had to set-up the ups w/ a newer Ubuntu release, test and trace using "upsmon -c fsd". And then, after comparing filesystems, realize the file was missing from xenial and simply copy it over. It took much longer than I'd expect due to the breadth of nut, not knowing if my hardware or conf settings were to blame (they weren't), and the expectation that things should "just work". I know, I probably shouldn't have a machine still running xenial :-P Alas, all is well now, and I've kissed apcupsd goodbye.

2 points by logicallee 3y ago

I'd like to hear some of your longest stories of bugs that were hard to fix but that you finally ended up fixing in the end! I want to hear your success stories! :) How did you finally fix it?

aastronaut 3y ago

Fixed a bug on how the browser wasn't closing TCP connections/Motion JPEG video streams properly in a responsive behavior. Took me about 3+ hours reading through various specs and that resulted to around 20 LOC changed. I then wrote a blog post about it[0], which took me about 10 days. [0]: https://blog.whilenot.dev/posts/cool-bugs-vs-shitty-bugs-part-1/ https://blog.whilenot.dev/posts/cool-bugs-vs-shitty-bugs-par...

tlesko 3y ago

I remember the first time I wanted to install Android Studio. The problem was that the name of my user in Windows had an accent, and for some reason it wasn't installed correctly (I don't remember it that well, it was a long time ago). What I did was just changing the user name. The problem with this is that i tried a lot more that just this, I hand't except this could be the problem.

acemarke 3y ago

I wrote up several debugging stories on my blog a while back: https://blog.isquaredsoftware.com/2019/01/blogged-answers-debugging-tips/#tales-of-debugging https://blog.isquaredsoftware.com/2019/01/blogged-answers-de... (I think the "6 hours to change the case of 1 letter in a filename" is still the most amusing one!)

reliefcrew 3y ago

There are many, of course, but this one is somewhat recent. The story isn't long but finding/fixing it was certainly infuriating. For some reason xenial's nut-server package is missing "/lib/systemd/system-shutdown/nutshutdown" I had to set-up the ups w/ a newer Ubuntu release, test and trace using "upsmon -c fsd". And then, after comparing filesystems, realize the file was missing from xenial and simply copy it over. It took much longer than I'd expect due to the breadth of nut, not knowing if my hardware or conf settings were to blame (they weren't), and the expectation that things should "just work". I know, I probably shouldn't have a machine still running xenial :-P Alas, all is well now, and I've kissed apcupsd goodbye.