Codeberg/Community
54
325
Fork
You've already forked Community
12

Internal server error on pull request #1952

Closed
opened 2025年05月28日 20:57:59 +02:00 by Baleine · 17 comments

Comment

Hi,

Since one hour ago, I am getting a 500 internal server error page on pull requests to the guix/guix repository. Other people also get the message.

See for example guix/guix#118

This doesn’t seem to happen on other repositories.

Could you take a look?

Thanks,
Noé

### Comment Hi, Since one hour ago, I am getting a 500 internal server error page on pull requests to the guix/guix repository. Other people also get the message. See for example https://codeberg.org/guix/guix/pulls/118 This doesn’t seem to happen on other repositories. Could you take a look? Thanks, Noé

Hi, was a review request for a team added?

Hi, was a review request for a team added?
Author
Copy link

It was probably automatically assigned to team-python by the CODEOWNERS file, yes.

It was probably automatically assigned to team-python by the CODEOWNERS file, yes.

Is it possible this team no longer exists?

Is it possible this team no longer exists?
Author
Copy link

It’s possible.

There is a script that deletes all teams and recreates them according to the etc/teams.scm file. Though I don’t know if it has been ran.

It’s possible. There is a script that deletes all teams and recreates them according to the etc/teams.scm file. Though I don’t know if it has been ran.

Yeah, it's quite likely the 500 is there because the review request references a deleted team.

Yeah, it's quite likely the 500 is there because the review request references a deleted team.
Author
Copy link

It’s very likely it has been ran after commit guix/guix@848ebb7f72. Which coincedes with the time that it broke.

CC @civodul

It’s very likely it has been ran after commit https://codeberg.org/guix/guix/commit/848ebb7f72fa529b0a3da47fbef2a6cf6f7fba8a. Which coincedes with the time that it broke. CC @civodul
Author
Copy link

Is there a good way to fix it?

Is there a good way to fix it?

I will try to get a fix in to avoid erroring when this happens. Although another suggestion might be to try and re-use the existing teams, as older PRs will otherwise show "requested review from ghost" or something along those lines.

I will try to get a fix in to avoid erroring when this happens. Although another suggestion might be to try and re-use the existing teams, as older PRs will otherwise show "requested review from ghost" or something along those lines.
Author
Copy link

For sure, we will update the script. Thanks for looking into this!

For sure, we will update the script. Thanks for looking into this!

@Gusted Thanks for the quick feedback.

We maintain our team list and members in a script, which currently blindly deletes and recreates teams as a way to make sure they are in sync with what’s defined in our file.

This seemed to work fine in my limited testing, but I hadn’t realized this could break Forgejo assumptions behind the scenes. I’ll change the script accordingly.

In the meantime, could Forgejo assume that a "ghost team" is equivalent to a same-named team, instead of marking it as ghost?

@Gusted Thanks for the quick feedback. We maintain our team list and members in a script, which currently [blindly deletes and recreates teams](https://codeberg.org/guix/guix/src/branch/master/etc/teams.scm#L311) as a way to make sure they are in sync with what’s defined in our file. This seemed to work fine in my limited testing, but I hadn’t realized this could break Forgejo assumptions behind the scenes. I’ll change the script accordingly. In the meantime, could Forgejo assume that a "ghost team" is equivalent to a same-named team, instead of marking it as ghost?

@civodul wrote in #1952 (comment):

but I hadn’t realized this could break Forgejo assumptions behind the scenes

Forgejo should handle this, this specific code was only touched recently and deleted teams are quite rare.@civodul wrote in #1952 (comment):

In the meantime, could Forgejo assume that a "ghost team" is equivalent to a same-named team, instead of marking it as ghost?

forgejo/forgejo#7987 will describe deleted teams as ghost teams in the requested reviews messages. There's not really a way to recover more information beyond that.

@civodul wrote in https://codeberg.org/Codeberg/Community/issues/1952#issuecomment-4902399: > but I hadn’t realized this could break Forgejo assumptions behind the scenes Forgejo should handle this, this specific code was only touched recently and deleted teams are quite rare.@civodul wrote in https://codeberg.org/Codeberg/Community/issues/1952#issuecomment-4902399: > In the meantime, could Forgejo assume that a "ghost team" is equivalent to a same-named team, instead of marking it as ghost? https://codeberg.org/forgejo/forgejo/pulls/7987 will describe deleted teams as ghost teams in the requested reviews messages. There's not really a way to recover more information beyond that.
Author
Copy link

Thanks for coding the fix! Do you have an estimate for when it will be deployed?

We would appreciate if it could go the hotfix way, since it affects about 95 pull requests. And we only moved here 3 days ago!

No pressure though, and thanks again.

Thanks for coding the fix! Do you have an estimate for when it will be deployed? We would appreciate if it could go the hotfix way, since it affects about 95 pull requests. And we only moved here 3 days ago! No pressure though, and thanks again.

Likely tomorrow, no promises.

Likely tomorrow, no promises.

guix/guix#104 is also broken

https://codeberg.org/guix/guix/pulls/104 is also broken

Bug fix was deployed on Codeberg.

Bug fix was deployed on Codeberg.
Author
Copy link

Thanks a lot! We are so back 😎

P.S. wasn’t it supposed to say "ghost team"? I see no reviews now. No big deal though.

Thanks a lot! We are so back 😎 P.S. wasn’t it supposed to say "ghost team"? I see no reviews now. No big deal though.

@Baleine wrote in #1952 (comment):

P.S. wasn’t it supposed to say "ghost team"? I see no reviews now. No big deal though.

It's only mentioned in the timeline. The sidebar is a different story.

@Baleine wrote in https://codeberg.org/Codeberg/Community/issues/1952#issuecomment-4913181: > P.S. wasn’t it supposed to say "ghost team"? I see no reviews now. No big deal though. It's only mentioned in the timeline. The sidebar is a different story.
jasewolf referenced this issue from a commit 2025年07月16日 05:53:10 +02:00
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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#1952
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?