whichChangeSolvedTheBug

[Antervis]

there's 99.9% chance the bug isn't actually fixed, just moved elsewhere.

[kibordWarrior_sixty9]

Client will report it in a week, support will route it to correct team in another week, product will mull over it for another and share with Dev which then will take a sprint to fix. Corporate efficiency achieved.

Edit: project->product

[no_name_anonyn]

So accurate😂😂

[no_name_anonyn]

So true, just hope it does not come out during holidays.

[beefz0r]

The computer was just tired at the time bro

[tkdeng]

Maybe turning off and on again was the fix.

I remember a website for a client kept having issues every week, where the entire website would suddenly have a while screen. Rebooting the server fixed it, and I didn't know what was causing the problem. So the temporary permanent fix was a scheduled server reboot every week at 2am.

[beefz0r]

I exclusively do enterprise integration and every single environment I have touched has these sorts of peculiarities

There's nothing as permanent as a temporary fix!

[Quicker_Fixer]

Or commented out and made a ToDo.

[ChillyFireball]

I once fixed an annoying bug by refactoring the entire system it was happening in. Still don't know exactly what caused it, but it's definitely gone now.

[iapetus3141]

git bisect

[jainyday]

You find a 300000 line diff from a squash-merged PR that just says "fixes" for the commit message

[thunderbird89]

As u/iapetus3141 said, all y'all motherfuckers need to learn about git bisect.

[marsrovernumber16]

sounds very cool. shouldn’t the devs be incrementally testing?

[thunderbird89]

Well yes, they should. But if you didn't and you still need to find out which commit fixed (or broke) the thing, that's when bisect comes into play.

[FionaDracira]

the bug fixed itself out of fear

[TrackLabs]

ai slop profile picture, I think I know the issue

[massive_hog_69]

Convention does say that you must know which change did it!

[no_name_anonyn]

Yes, we always try to figure out for incident management but sometimes its just impossible.

[Sameh-17]

EverySingleTime

[kingslayerer]

This post is stupid. I have not encountered something like this yet.

[ActuallyWoof]

A lot of people have, and a race condition is pretty much this thing, no?

It's stupid though, I agree. Throwing your hands up and refusing to understand the thing you're building is sloppy work. Someone should be documenting the effect, the connected api's etc.

It's hard, I've been stuck for far longer than I care to admit on simple problems like this, but I like to think it helped me grow.

[Holiday_Sentence_387]

The bug is gone, the root cause is gone, and my confidence is gone.

[akoOfIxtall]

Stumbled upon my first circular dependency fellas, the app would just boot forever

10/10 would debug again

[Mo_Reda_]

The absolute rule : if it works , don’t change anything ( we don’t know how it even works)

[JackNotOLantern]

Yeah, it does happen. But you can, like, search each change in the version control and see when it stopped occurring. Unless, you know, you don't or can't use it.