PR creation returns HTTP 500 on public repo (works on private repo in same org) #2798

StandingRecord-Editor commented 2026年06月24日 02:58:46 +02:00

Comment

Since yesterday evening, we are unable to create pull requests on our public repository StandingRecord/StandingRecord. Both the web UI and the API return an internal server error.

API response:

POST /api/v1/repos/StandingRecord/StandingRecord/pulls
→ HTTP 500: {"message":"","url":"https://codeberg.org/api/swagger"}

The web UI compare page (/compare/main...{branch}) also returns an internal server error when the form is submitted.

What we've tried:

• Creating PRs from multiple different branches (including a trivial single-line change on a fresh branch off main)
• Pushing a new commit to main to trigger a resync
• Both the API and web UI fail consistently

What works:

• Viewing existing open PRs on the repo is fine
• Pushing commits and creating branches works normally
• Merging an already existing PR works normally
• PR creation on our private repo in the same org (StandingRecord/StandingRecord-engine) works fine — we successfully opened a PR there while troubleshooting this

This appears to be specific to the StandingRecord/StandingRecord repository. Any help appreciated.

### Comment Since yesterday evening, we are unable to create pull requests on our public repository [StandingRecord/StandingRecord](https://codeberg.org/StandingRecord/StandingRecord). Both the web UI and the API return an internal server error. **API response:** ``` POST /api/v1/repos/StandingRecord/StandingRecord/pulls → HTTP 500: {"message":"","url":"https://codeberg.org/api/swagger"} ``` The web UI compare page (`/compare/main...{branch}`) also returns an internal server error when the form is submitted. **What we've tried:** - Creating PRs from multiple different branches (including a trivial single-line change on a fresh branch off main) - Pushing a new commit to main to trigger a resync - Both the API and web UI fail consistently **What works:** - Viewing existing open PRs on the repo is fine - Pushing commits and creating branches works normally - Merging an already existing PR works normally - PR creation on our private repo in the same org (`StandingRecord/StandingRecord-engine`) works fine — we successfully opened a PR there while troubleshooting this This appears to be specific to the `StandingRecord/StandingRecord` repository. Any help appreciated.

martinsnygg commented 2026年06月30日 11:15:04 +02:00

Same symptom on another public repo, since today (2026年06月30日).

Repo: martinsnygg/stratintel (public, repo id 1043940)
Last successful PR: #460, created 2026年06月19日 18:15 +02:00
First observed failure: 2026年06月30日 (first PR attempt since #460)

All three PR-creation paths fail with the same internal server error, while
everything else on the repo works normally — matching #2798 and #2739.

1. REST API

POST /api/v1/repos/martinsnygg/stratintel/pulls
→ HTTP 500: {"message":"","url":"https://codeberg.org/api/swagger"}

Fails identically with a full payload and with a minimal {title, head, base}.

2. Web UI — /compare/main...refactor/shared-llm-client returns an
internal server error on submit.

3. AGit (SSH) — git push origin HEAD:refs/for/main is rejected:

remote: Forgejo: Internal Server Error (no message for end users)
remote: error: proc-receive exited abnormally
! [remote rejected] HEAD -> refs/for/main (fail to run proc-receive hook)

What still works:

• Pushing commits / creating branches (the branch is up on the remote fine)
• Reading existing open PRs and all other repo API endpoints
• (Cannot test merging — there is no open PR to merge)

Tried without success:

• Multiple head branches, including a fresh single-purpose branch off the
  same commit
• Minimal vs. full API payloads
• Several retries with backoff over ~15 min

Looks like the same "repo enters a broken PR-creation state" condition as
#2739 (their last good PR 2026年05月30日 → broke 2026年06月07日; ours #460
2026年06月19日 → broken by 2026年06月30日). Happy to provide more details or test
against this repo. CC @gusted

Same symptom on another **public** repo, since today (2026年06月30日). **Repo:** `martinsnygg/stratintel` (public, repo id `1043940`) **Last successful PR:** #460, created 2026年06月19日 18:15 +02:00 **First observed failure:** 2026年06月30日 (first PR attempt since #460) All three PR-creation paths fail with the same internal server error, while everything else on the repo works normally — matching #2798 and #2739. **1. REST API** POST /api/v1/repos/martinsnygg/stratintel/pulls → HTTP 500: {"message":"","url":"https://codeberg.org/api/swagger"} Fails identically with a full payload and with a minimal `{title, head, base}`. **2. Web UI** — `/compare/main...refactor/shared-llm-client` returns an internal server error on submit. **3. AGit (SSH)** — `git push origin HEAD:refs/for/main` is rejected: remote: Forgejo: Internal Server Error (no message for end users) remote: error: proc-receive exited abnormally ! [remote rejected] HEAD -> refs/for/main (fail to run proc-receive hook) **What still works:** - Pushing commits / creating branches (the branch is up on the remote fine) - Reading existing open PRs and all other repo API endpoints - (Cannot test merging — there is no open PR to merge) **Tried without success:** - Multiple head branches, including a fresh single-purpose branch off the same commit - Minimal vs. full API payloads - Several retries with backoff over ~15 min Looks like the same "repo enters a broken PR-creation state" condition as #2739 (their last good PR 2026年05月30日 → broke 2026年06月07日; ours #460 2026年06月19日 → broken by 2026年06月30日). Happy to provide more details or test against this repo. CC @gusted