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:

  1. Your software isn’t working. Vince McMahon looks curious.
  2. The bug is in a library. McMahon smiles.
  3. There already is an issue on Github. McMahon makes an orgiastic face.
  4. They published a fix last week. [I don’t know how to describe the face McMahon is making.]
  • AwkwardLookMonkeyPuppet
    45•9 months ago
    • The bug is from a library
    • There are 5 dozen related bugs on GitHub
    • The last commit to the library was 3 years ago
  • ivanafterall
    22•9 months 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.

  • @[email protected]
    6•8 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.

  • @Michal
    5•8 months ago

    And the library update isn’t published for 6 months

  • @[email protected]
    3•9 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.