- cross-posted to:
- genzedong
- cross-posted to:
- genzedong
Does anyone have any idea how this bug occurs? I’ve been thinking about it, but do not know enough about net code or web design to give more than rudimentary guesses. Furthermore, are their anyways in which this could be exploited in a harmful manner against Lemmygrad, or should it be a low priority bug fix? Any answers are appreciated, Thank you!
You must log in or register to comment.
I think the bug triggers when the only commenter on someone’s post deletes said comment
My guess is it has something to do with how Lemmy updates the comment count on a post when a comment is deleted, maybe it calls the function responsible for that twice, improperly calculates how many comments were actually removed, etc. This is definitely not exploitable, it’s just an issue calculating the count.
It’s probably related to federation. @dessalines@lemmy.ml @nutomic@lemmy.ml is there an issue for this?
There does seem to be: https://github.com/LemmyNet/lemmy/issues/2557
Yup that’s the issue. Its a sql trigger one for the aggregate counts. Not a huge deal atm.
Oh I see. Thank you!
Sorry guys, this one’s on me. It was late and I misread the article and didn’t realize till after I commented, and at that point it was to late to salvage the comment.
It’s not a problem, this has happened many times before. If you look at the screenshot in the issue link I posted earlier, that one has -5 comments.
Be thankful it was a signed integer. Otherwise we’d have to deal with eighteen trillion, four-hundred and forty-six thousand billion, seven-hundred and forty-four billion, seventy-three thousand million, seven-hundred and nine million, five-hundred and fifty one thousand, six-hundred and fifteen comments.
I hadn’t even thought of that! Your right, as entertaining as that would be you’d see libs declairing our attempt to appear more popular than we realy are or some other non-sense.
