I think I accidentally gave a repo -1 stars... #2376

Open
opened 2026-02-13 20:01:59 +01:00 by mxace · 3 comments

Comment

I tried unstarring a repository, but it didn't get through, so I refreshed and tried again, until at one point I refreshed and saw that the repo now has -1 stars.

When I look at who has starred the repo it still shows 1 person. Surely Codeberg, or maybe even Forgejo itself, has automations that automatically fix the count, right...?

Still felt like I should mention it though.

### Comment I tried unstarring [a repository](https://codeberg.org/inomotech/shared-actions-workflows/), but it didn't get through, so I refreshed and tried again, until at one point I refreshed and saw that the repo now has -1 stars. When I look at who has starred the repo it still shows 1 person. Surely Codeberg, or maybe even Forgejo itself, has automations that automatically fix the count, right...? Still felt like I should mention it though.
Author

My Starred repositories also says -2 now..

[My Starred repositories](https://codeberg.org/mxace?tab=stars) also says -2 now..
Owner

@mfenniak: Do you want to look into this by chance? Anything we could provide for debugging here?

@mfenniak: Do you want to look into this by chance? Anything we could provide for debugging here?

I don't think there's much value in digging through logs to try to find a root cause. These fields weren't factors in my deadlock work because it was focused on making sure everything in the path of a PR merge was safe. The num_stars stat on the user and repo are among many fields that weren't addressed.

They should either go through a conversion into an async stat (like forgejo/forgejo#9916) if they're used in sorting and need to remain in a database table, or into a cached stat (like forgejo/forgejo#9927) otherwise.

I'm juggling quite a few projects at the moment and don't have space to do more work like this in the short-term, but I'll keep it on my radar for when some of those other efforts are complete.

I don't think there's much value in digging through logs to try to find a root cause. These fields weren't factors in my deadlock work because it was focused on making sure everything in the path of a PR merge was safe. The `num_stars` stat on the user and repo are among many fields that weren't addressed. They should either go through a conversion into an async stat (like https://codeberg.org/forgejo/forgejo/pulls/9916) if they're used in sorting and need to remain in a database table, or into a cached stat (like https://codeberg.org/forgejo/forgejo/pulls/9927) otherwise. I'm juggling quite a few projects at the moment and don't have space to do more work like this in the short-term, but I'll keep it on my radar for when some of those other efforts are complete.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2376
No description provided.