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

Error 500 on pull request #2075

Open
opened 2025年08月11日 16:59:58 +02:00 by giri · 6 comments

Comment

Hi,

I have opened a pull-request and it cannot be viewed because of a 500 error:

De_Coder/Gadgetbridge#1

### Comment Hi, I have opened a pull-request and it cannot be viewed because of a 500 error: De_Coder/Gadgetbridge#1

Hi, did you create a pull request with many (>2K) commits?

Hi, did you create a pull request with many (>2K) commits?
Author
Copy link

Nope this pull request only has like 5 commits.

Here is the branch: https://codeberg.org/giri/Gadgetbridge/src/branch/ring-sr08

I did rebase the upstream main.

Nope this pull request only has like 5 commits. Here is the branch: https://codeberg.org/giri/Gadgetbridge/src/branch/ring-sr08 I did rebase the upstream main.

I think you might have created a bigger PR than you realized, the database says that there have been more than 2K commits (and got caught by text limit that records the pushed commit IDs).

I think you might have created a bigger PR than you realized, the database says that there have been more than 2K commits (and got caught by text limit that records the pushed commit IDs).
Author
Copy link

@Gusted wrote in #2075 (comment):

I think you might have created a bigger PR than you realized, the database says that there have been more than 2K commits (and got caught by text limit that records the pushed commit IDs).

You seem to be right, the upstream was pretty active in the meanwhile. What to do now? The rebase itself makes sense to me...

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2075#issuecomment-6321391: > I think you might have created a bigger PR than you realized, the database says that there have been more than 2K commits (and got caught by text limit that records the pushed commit IDs). You seem to be right, the upstream was pretty active in the meanwhile. What to do now? The rebase itself makes sense to me...

I don't think you can propose a rebase to an existing PR via another PR, the original author would have to do and force-push its result.

I don't think you can propose a rebase to an existing PR via another PR, the original author would have to do and force-push its result.
Author
Copy link

@Gusted wrote in #2075 (comment):

I don't think you can propose a rebase to an existing PR via another PR, the original author would have to do and force-push its result.

How sad, that is a valid use case.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2075#issuecomment-6372127: > I don't think you can propose a rebase to an existing PR via another PR, the original author would have to do and force-push its result. How sad, that is a valid use case.
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
2 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#2075
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?