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.]

top 11 comments

sorted by: hot top controversial new old

[–] Anticorp@lemmy.world 44 points 10 months ago (1 children)

The bug is from a library
There are 5 dozen related bugs on GitHub
The last commit to the library was 3 years ago

[–] bigboismith@lemmy.world 7 points 10 months ago

Library is a read-only repo
last commit was 10 years ago

[–] fckreddit@lemmy.ml 14 points 10 months ago

And then you wake up.

[–] lugal@sopuli.xyz 11 points 10 months ago (2 children)

Your deadline is tomorrow

[–] bleistift2@feddit.de 10 points 10 months ago

Time to write a ‘Known limitations’ section.

[–] Dempf@lemmy.zip 4 points 10 months ago (1 children)

Time to compile it myself.

[–] lugal@sopuli.xyz 1 points 10 months ago

I'm tired, I thought it's published next week

[–] superfes@lemmy.world 9 points 10 months ago

This has happened to me once, in 20 years of development.

That's pretty good.

[–] Michal@programming.dev 5 points 10 months ago

And the library update isn't published for 6 months

[–] Luvon@beehaw.org 5 points 10 months ago

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.

[–] 4z01235@lemmy.world 3 points 10 months ago

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.