I just love it when the debugger integration into the IDE breaks for no good reason.

I also love that the github issue about it was closed for inactivity. Because problems magically disappear if no one screams "same issue here" for long enough.
Fuck you too

ran across a similar issue: weird behaviour happening in what I'm doing, there is an issue created in 2017 and closed due to inactivity, with no answers. Naturally, people would keep on complaining if the issue was true. Since it died out quietly, I assumed I and that poor chap were doing something wrong. And that's indeed true - I was doing it wrong!

What I meant to say is if there's an issue ticket created that died quietly with no activity or followups, chances are you and the creator of the ticket both are doing something wrong.

@AvatarOfKaine TIL Raul Julia played a software engineer.

The guy is talented!

I haven't used the integration part of IDEs in forever because they won't work 100% of the time. Know what does work 100% of the time? Just running the code with debug loggers injected in.

Regarding Github-Issues closed for inactivity:

It's sad to say but I can understand why after having worked in a team where we have a bi-monthly rundown of all issues.

If we have an issue that's been brought up multiple times but is hard to reproduce or ends up being waaaay down the priority list - this often results in the team saying "We're spending too much time talking about issues we're not planning on working on soon. How bout closing them, if they are really bad they'll come up again"

I used to dislike this approach. I used to say "let's just tag it so we can hide it with a filter".

But to some extent, that is what closing an issue does. gets it out of your way.

The lame part is that users will have a harder time finding it to add additional info.

@sariel It has merit, yes. On the other hand, I understand it might be a pain to figure out why it crashed. Unless you know how. Logs, threaddumps, coredumps, strace - ... yeah. You're lucky if you know your IDE is logging and where these logs are. Otherwise, you're elbows deep in some shit trying to debug an app that's not yours and you have no src of, to figure out what you've done wrong. Especially if you have not changed anything during the timeframe between it working and stopping to work.

P.S. in the case of JetBrains IDEs, it's usually the plugins that mess everything up

@netikras @jiraTicket the worst part about this is that the reason for the issue is actually shown perfectly well in those issue reports
I'd link them but I'm not at work so I dont have the links

But tldr: the people in the issue have made a workaround that "fixes" it, but the actual fix for the software never came

@LotsOfCaffeine I hear you. I’m subscribed to some issues like that in repos I use. Sometimes it’s gone so far that these issues are 4 years old and are linked to in stackOverflow as ”this is The Solution, the fix is there, but you gotta do it yourself cause the issue is ignored”

I figure there is often an explanation - ranging from ”there’s just more high prio tasks” to ”we have a refactor planned so this problem and solution will be different soon. Waste of time to solve it right now”

But I feel like these reasons are often never communicated. If the repo maintainer would just write a small comment at least once a year saying ”I know it sucks this is still an issue but it’d because…” that would at least make users feel less ignored

… That being said: I kinda understand why they don’t.
Maybe they have tried it but got a massive amount of shit the second time they said ”Sorry we’re aware of the issue but we just don’t have time to prioritize it”

Cause then people will say ”WTF, this takes 1 minute to implement - there’s suggested code in the issue!” Or ”You’ve said this 2 years in a row, you suck”

I bet as a maintainer it feels worse to make updates that get hate than to just forget it until you know you’ll do something about it

As a user I get it: this one issue is my biggest problem. But there’s probably 78 other bigger tasks the maintainer wants to do.

@jiraTicket yeah I get that maintainers time is very much limited.
Its just a bit of a middle finger if a bot comes along and closes it when there's not even a response from the maintainers

@sariel integration ? as in adding things to the ide that work with your software system ?

why would a strip club charge equal price for women to get in ? :P

this new frightening world with its flashy light and overly 'sophisticated' dialect scares a cave man like me LOL

@AvatarOfKaine yeah, as-in integrating with your local development environment for adding breakpoints and other nifty shit.

@sariel I didn't read her post apparently
Mean da remote gdb style of integration?

@AvatarOfKaine no, local. It's really no different these days though.

I run 100% containerized now so it's not a big deal.

The hardest part is finding an IDE that just doesn't suck right ootb.

@sariel I really have only used visual studio and vs code honestly

Unless you count the old turbo projects by Borland

Or pycharm

@sariel netbeans and eclipse start too god-damned slow or used to

@sariel I wish I'd had the build a compiler final project sigh