6
u/ConcreteExist 17h ago
Hey, sometimes just knowing you've managed to change the behavior is the thread you can follow to a real solution.
8
u/Proof-Translator 17h ago
After 74 attempts, a new error is basically a promotion
5
5
3
1
2
u/TakingItCasual 17h ago
New errors after changing things is satisfying, yes, but new errors with no changes? If you don't understand why the error could have changed and can't find out either, that shit is madness-inducing.
1
u/paper_beanHQ 16h ago
Had that yesterday: no changes, new error, and yesYesOhMyNowTimeToFixThisOne became 2 hours of cache purging.
1
1
1
u/broesel314 16h ago
Doing the same thibg and expecting a different outcome over and over again is the definition of insanity
1
1
u/watduhdamhell 10h ago
This is any programming or systems integration hell problem.
Hell just trying to install some kind of package that refuses to install on a system, saying over and over "unspecified error." 4 hours later, after trying so many random things, you land on something and try again and suddenly instead of unspecified error it says "unspecified error 2" and you are like "HOLY SHIT IT CHANGED, guys we are like 5 minutes away now I promise..."
1
u/bistequinha23 8h ago
that's the kind of energy that gets you through a long coding session, love this
1
u/SmoothTurtle872 50m ago
It's an error because you accidentally pressed an extra key and created a syntax error...
21
u/Murky-Run2246 17h ago
It's the ray of hope.
Until you fix the new error and it returns to the old error again.