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.]
  • BassaForte@lemmy.worldEnglish
    1·
    6 months ago

    Or in my case… The bug has been fixed in a PR that’s been open for the last 4 years and the repo owner refuses to merge it.

      • BassaForte@lemmy.worldEnglish
        0·
        6 months ago

        I know that’s an option, and others have done just that. I just wish the owner would get the stick out of their ass and merge an obvious improvement.

  • Pyro@lemmy.worldEnglish
    0·
    6 months ago

    I would say finding that the bug is in a library is worse than finding it in your own code.

    If it’s your own code, you just fix it.

    If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.

    Yeah, I’d take my own bugs over library bugs any day.

  • bigkahuna1986@lemmy.ml
    0·
    6 months ago

    Sometimes the issue is marked as fixed but a new version won’t be coming out for months and you’re simply told to compile it yourself only to find it has literally hundreds of carefully tuned compilation dependencies and environment specific settings that aren’t documented.

  • Otter@lemmy.caEnglish
    0·
    6 months ago

    The best coincidence I got was “6 hours ago”

    I got to leave the “thank you, it worked” confirmation comment

  • Phen@lemmy.eco.br
    0·
    6 months ago

    They changed their dependencies and now your stack no longer supports the lib until you fix your whole framework to work with the up-to-date stuff.