Yeah, it was the cached dependencies, how did you guess?
mprogrammerhumor·Programmer Humorbymerthyr1831 I spent a week debugging a build issueYeah, it was the cached dependencies, how did you guess?View original on lemmy.ml84Comments6Reply
Björn swg-empire.deThere are two hard problems in computer sciences. Cache invalidation, naming things and off by one errors.27Reply
HHubertManne piefed.socialUgh. When I can't solve something in a day the imposter syndrome starts breathing down my neck.20Reply
PPunkRockSportsFan fanaticus.social1Hide 1 replyHahaaa the first thing you checked too? But didn’t realize it was that until way later? That’s me!15Reply
mmerthyr1831 replylemmy.mlYup. I got our QA guy to help debug it and he was like "maybe just dont upgrade the dodgy dependency and delete your cache" lmfao yup fixed it21Reply
iiglou programming.dev1Hide 1 replyIf something should work, but it doesn't, nuke all the caches before diving in the rabbit hole of debugging weird issues8Reply
6 replies
There are two hard problems in computer sciences. Cache invalidation, naming things and off by one errors.
Ugh. When I can't solve something in a day the imposter syndrome starts breathing down my neck.
Hahaaa the first thing you checked too? But didn’t realize it was that until way later? That’s me!
Yup. I got our QA guy to help debug it and he was like "maybe just dont upgrade the dodgy dependency and delete your cache" lmfao yup fixed it
If something should work, but it doesn't, nuke all the caches before diving in the rabbit hole of debugging weird issues
We literally have a "pnpm nuke" command to help us with that.