660
Sometimes things do go your way (feddit.de)
submitted 10 months ago by bleistift2@feddit.de to c/programmerhumor@lemmy.ml
30 comments fedilink hide all child comments

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.]
top 30 comments
sorted by: hot top controversial new old
[-] bigkahuna1986@lemmy.ml 72 points 10 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.

[-] MonkderZweite@feddit.ch 7 points 10 months ago* (last edited 10 months ago)

What are you trying to build, the equivalent to a death star?

[-] zerofk@lemm.ee 8 points 10 months ago

Hello world.

[-] crandlecan@mander.xyz 4 points 10 months ago

Opensource is the best!! 😅

[-] BautAufWasEuchAufbaut@lemmy.blahaj.zone 25 points 10 months ago

Open source has no tangible effect on release schedules?
If the software in question was proprietary you wouldn't even have that option. Distro packages could backport that fix too.

[-] BassaForte@lemmy.world 57 points 10 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.

[-] DmMacniel@feddit.de 17 points 10 months ago

Fork it. Integrate the PR Branch. Build it... and pray :)

[-] BassaForte@lemmy.world 24 points 10 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.

[-] Steve@startrek.website 7 points 10 months ago

Maybe they have more important shit to do

[-] Radium@sh.itjust.works 32 points 10 months ago

But you are 20 versions each with breaking changes behind…

[-] DieguiTux8623@feddit.it 4 points 10 months ago

This.

[-] Phen@lemmy.eco.br 30 points 10 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.

[-] WhiskyTangoFoxtrot@lemmy.world 26 points 10 months ago

The new version isn't backward-compatible and now you've got to re-write your whole project.

[-] Lemminary@lemmy.world 8 points 10 months ago

Conversely: The new version requires you write it with a different word that makes more sense, so you do an search and replace in a few files and get done with it and nothing breaks.

[-] bleistift2@feddit.de 1 points 10 months ago

If you edit code with find/replace, you need a better IDE. Just a hint.

[-] Lemminary@lemmy.world 1 points 10 months ago

I'm aware, and I do use a good IDE, but I'm simplifying the operation here for the punch line.

[-] Pyroglyph@lemmy.world 24 points 10 months ago* (last edited 10 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.

[-] SpaceCadet@feddit.nl 7 points 10 months ago

If there isn’t one

Worse is if there is one but it says: [OPEN] Opened 7 years ago Updated 2 days ago, with a whole bunch of people commenting the equivalent of "me too", and various things they tried to solve it, but no solution.

[-] bleistift2@feddit.de 2 points 10 months ago

That’s where my ecosystem shines, since it’s all open source. If there’s a bug that I can fix, but the maintainer won’t, I’ll just fork the repo.

[-] otter@lemmy.ca 24 points 10 months ago

The best coincidence I got was "6 hours ago"

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

[-] avidamoeba@lemmy.ca 22 points 10 months ago

The software is deployed on Ubuntu LTS in prod.

[-] FiskFisk33@startrek.website 10 points 10 months ago

see you in about fifteen years

[-] kogasa@programming.dev 4 points 10 months ago

Ubuntu LTS

More like RHEL 5

[-] DrMango@lemmy.world 12 points 10 months ago

Sometimes I feel slightly robbed when this happens. Like damn I was just gearing up for a marathon troubleshooting session and now I just get to use the software as intended?

[-] owen@lemmy.ca 1 points 10 months ago

Lol! Sometimes after configuration/troubleshooting I just log off feeling content, despite never actually starting what I set out to do 🤣

[-] Chais@sh.itjust.works 12 points 10 months ago

But you're running Debian, so it'll be 2 years at least before you get it.

[-] darkfarmer@sh.itjust.works 4 points 10 months ago

This gave me a boner

[-] Undertaker@feddit.de 4 points 10 months ago

The issue was closed as beging fixed but it isn't.

So often...

[-] toastal@lemmy.ml 3 points 10 months ago

You mean the patchset was on the mailing list & applying the patch was a simple Nix overlay?

[-] barsoap@lemm.ee 0 points 10 months ago

You know, just today I happened to try out getting earlyoom killer notifications on my desktop and wondered why they don't work.

this post was submitted on 18 Jan 2024
660 points (98.0% liked)

Programmer Humor

32588 readers
913 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
cat_programmer@lemmy.ml
AgreeableLandscape@lemmy.ml