500 error creating pull request #2473

New Issue

GiteaMirror · 2025-11-02T04:37:40-06:00

GiteaMirror commented

2025-11-02 04:37:40 -06:00

Originally created by @zaaksam on GitHub (Oct 31, 2018).

Gitea version (or commit ref): 31a738b (by docker image gitea/gitea:1.5.2)
Operating system: macOS 10.14
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [ x ] Not relevant

Description

log:

[...routers/repo/pull.go:803 CompareAndPullRequestPost()] [E] GetPatch: signal: killed

Originally created by @zaaksam on GitHub (Oct 31, 2018). - Gitea version (or commit ref): 31a738b (by docker image gitea/gitea:1.5.2) - Operating system: macOS 10.14 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ x ] Not relevant ## Description log: ``` [...routers/repo/pull.go:803 CompareAndPullRequestPost()] [E] GetPatch: signal: killed ```

GiteaMirror added the issue/stale type/bug issue/needs-feedback labels 2025-11-02 04:37:40 -06:00

GiteaMirror closed this issue

2025-11-02 04:37:40 -06:00

GiteaMirror commented

2025-11-02 04:37:41 -06:00

@lafriks commented on GitHub (Nov 11, 2018):

Could this be memory related?

@lafriks commented on GitHub (Nov 11, 2018): Could this be memory related?

GiteaMirror commented

2025-11-02 04:37:41 -06:00

@lafriks commented on GitHub (Nov 11, 2018):

This would also need more information on how to reproduce this

@lafriks commented on GitHub (Nov 11, 2018): This would also need more information on how to reproduce this

GiteaMirror commented

2025-11-02 04:37:41 -06:00

@zaaksam commented on GitHub (Nov 13, 2018):

I clicked the "NewPullRequest", and then change the "merge into" branch, it happened.

It is normal for others to create PR.

@zaaksam commented on GitHub (Nov 13, 2018): I clicked the "NewPullRequest", and then change the "merge into" branch, it happened. It is normal for others to create PR.

GiteaMirror commented

2025-11-02 04:37:42 -06:00

@stale[bot] commented on GitHub (Jan 12, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 12, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:37:42 -06:00

@dmarov commented on GitHub (Jan 30, 2019):

encountered the same issue on FreeBSD 11.1-RELEASE-p13, Gitea version 1.6.4, DB_TYPE = sqlite3, seems like it is related to particular gitea user
log message:
[...routers/repo/pull.go:734 PrepareCompareDiff()] [E] GetDiffRange: ParsePatch: Unquote: invalid syntax
it disappears after user which creates pull request have been recreated

@dmarov commented on GitHub (Jan 30, 2019): encountered the same issue on FreeBSD 11.1-RELEASE-p13, Gitea version 1.6.4, DB_TYPE = sqlite3, seems like it is related to particular gitea user log message: [...routers/repo/pull.go:734 PrepareCompareDiff()] [E] GetDiffRange: ParsePatch: Unquote: invalid syntax it disappears after user which creates pull request have been recreated

GiteaMirror commented

2025-11-02 04:37:42 -06:00

@zeripath commented on GitHub (Jan 30, 2019):

What is the failing username? Did they have a valid email address?

@zeripath commented on GitHub (Jan 30, 2019): What is the failing username? Did they have a valid email address?

GiteaMirror commented

2025-11-02 04:37:43 -06:00

@dmarov commented on GitHub (Jan 30, 2019):

username: BuldakovIlya, had valid email address

@dmarov commented on GitHub (Jan 30, 2019): username: BuldakovIlya, had valid email address

GiteaMirror commented

2025-11-02 04:37:43 -06:00

@zeripath commented on GitHub (Jan 30, 2019):

Damn I was hoping the name was pathological somehow. There are several issues that my PR #5774 solved.

@zeripath commented on GitHub (Jan 30, 2019): Damn I was hoping the name was pathological somehow. There are several issues that my PR #5774 solved.

GiteaMirror commented

2025-11-02 04:37:43 -06:00

@stale[bot] commented on GitHub (Feb 18, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 04:37:44 -06:00

@zeripath commented on GitHub (Feb 18, 2019):

@dmarov were you able to ever get this bug to fire for other users, and after recreating the user did it is ever occur again?

Presumably that broken user was created in an earlier version of Gitea?

@zeripath commented on GitHub (Feb 18, 2019): @dmarov were you able to ever get this bug to fire for other users, and after recreating the user did it is ever occur again? Presumably that broken user was created in an earlier version of Gitea?

GiteaMirror commented

2025-11-02 04:37:44 -06:00

@dmarov commented on GitHub (Feb 18, 2019):

This bug fired just 2 times since we use gitea, it fired for me and for user I mentioned previously. no other occurencies. After recreating of user it didn't happen again. User was created in earlier version of gitea but now it is up to date.

@dmarov commented on GitHub (Feb 18, 2019): This bug fired just 2 times since we use gitea, it fired for me and for user I mentioned previously. no other occurencies. After recreating of user it didn't happen again. User was created in earlier version of gitea but now it is up to date.

GiteaMirror commented

2025-11-02 04:37:44 -06:00

@zeripath commented on GitHub (Feb 18, 2019):

Ok so I think this might have been a migration related issue.

If we can't get more information about it I don't think we can do more about it and we should leave this bug closed.

Hopefully, no one else will have this issue...

@zeripath commented on GitHub (Feb 18, 2019): Ok so I think this might have been a migration related issue. If we can't get more information about it I don't think we can do more about it and we should leave this bug closed. Hopefully, no one else will have this issue...

GiteaMirror commented

2025-11-02 04:37:44 -06:00

@bkmgit commented on GitHub (Oct 2, 2019):

Hi,
Getting this error on Gitea 1.9.3 running on Cent OS 7. It is possible to merge the pull requests using the command line on a different computer, for example following

Specifically, within the main repository one is working in, one can:

git remote add somefork https://my.gitea.ip:3000/cool/fork
git fetch somefork
git checkout master
git merge somefork/master
git push

@bkmgit commented on GitHub (Oct 2, 2019): Hi, Getting this error on Gitea 1.9.3 running on Cent OS 7. It is possible to merge the pull requests using the command line on a different computer, for example following * http://www.bartread.com/2014/02/12/git-basics-how-to-merge-changes-from-a-different-fork-into-your-own-branch/ * https://stackoverflow.com/questions/6022302/how-to-apply-unmerged-upstream-pull-requests-from-other-forks-into-my-fork and then pushing the changes Specifically, within the main repository one is working in, one can: git remote add somefork https://my.gitea.ip:3000/cool/fork git fetch somefork git checkout master git merge somefork/master git push

GiteaMirror commented

2025-11-02 04:37:45 -06:00

@lunny commented on GitHub (Oct 2, 2019):

@bkmgit please fire another issue.

@lunny commented on GitHub (Oct 2, 2019): @bkmgit please fire another issue.

GiteaMirror commented

2025-11-02 04:37:45 -06:00

@bkmgit commented on GitHub (Oct 2, 2019):

@lunny Thanks, done #8351

@bkmgit commented on GitHub (Oct 2, 2019): @lunny Thanks, done #8351

GiteaMirror referenced this issue

2025-11-02 12:10:09 -06:00