- cross-posted to:
- programmerhumor@lemmy.world
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.world
- programmerhumor@lemmy.ml
cross-posted from: https://feddit.de/post/7998794
cross-posted from: https://feddit.de/post/7998742
Meme transcription: 4 panels of Vince McMahon reacting increasingly ecstaticly to:
- Your software isn’t working. Vince McMahon looks curious.
- The bug is in a library. McMahon smiles.
- There already is an issue on Github. McMahon makes an orgiastic face.
- They published a fix last week. [I don’t know how to describe the face McMahon is making.]
You must log in or # to comment.
- The bug is from a library
- There are 5 dozen related bugs on GitHub
- The last commit to the library was 3 years ago
- Library is a read-only repo
- last commit was 10 years ago
Another version of this is unexpectedly finding some niche, single-developer software tool that does precisely the thing you need, all because some genius angel stranger (strangel?) from the internet happened to encounter the same problem, and somehow knew how to fix it.
And then you wake up.
Your deadline is tomorrow
Time to write a ‘Known limitations’ section.
Time to compile it myself.
I’m tired, I thought it’s published next week
This has happened to me once, in 20 years of development.
That’s pretty good.
The bug is in the library of a library that the library owns. They fixed it and published it in the library of the library but the library hasn’t been updated in 2 months.
And the library update isn’t published for 6 months
I just went through this exact process (not for the first time) two weeks ago with a bug in the golang standard library. Fun times. Deep in the dependency stack of a container build my team doesn’t own so who knows when I’ll get a fixed version.
