-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening a PR leads to 500 status - due to lfs hooks #16372
Comments
Hi, please provider server side logs, ideally from when you created the PR, and when visiting the PR page. Otherwise it's hard to debug the problem |
@DHentzschel Can you verify the path |
Hello, what log files could I provide in addition?
The path i.e. repo exists. I also can work with the repo local and push it to gitea but as soon as I want to open a PR, a 500 status code will be returned. |
have you sanitized these logs to remove the owner and reponames? |
The following (full) logs have been written: Frontend
Backend |
@DHentzschel I think we're going to need to see the command that gets sent to git . However, first please ensure that If you're certain that it exists and is a git repo then: Change your app.ini to set the following: RUN_MODE=dev # This is important as it will give us git command logging
...
[database]
LOG_SQL=false # We don't need to see SQL statements
...
[log]
MODE = console
LEVEL= debug
REDIRECT_MACARON_LOG=true
MACARON=console
ROUTER=console
XORM=console and then try to do the push again... Then give us the full logs. If you have to sanitize please really only sanitize the absolute minimum. Please note in the above configuration I am sending everything console for a reason. I need to see how things interleave. If you send these to files they will lose the interleaving and the git logs only get sent to the console anyway. (in 1.14 and lower - 1.15 will be better in this regard.) |
@zeripath After using your config parameters the following got printed to the console: I've preserved its integrity. By the way, after getting this error, a new pull request will be created and displayed like this: |
AHA! I've worked this out. This is not coming from Somehow you have raw |
See #13910 |
Glad to hear you figured it out. |
agh I missed this - you need to go into the repos on the filesystem and remove the git lfs hooks from the hooks directory. git lfs will have more information. |
1.14.4
2.20.1
Raspberry Pi OS Debian buster
[x]
):Description
When trying to open a PR from develop to master branch in a private, simple and small repo, Gitea returns
500
.After enabling debug and trace mode and retrying the same step, gitea's frontend prints the following message:
Push: <org>/<repo>:develop <org>/<repo>:refs/pull/18/head exit status 1 - Invalid remote name "/<path>/<to>/<org>/<repo>.git": Invalid remote name: "/<path>/<to>/<org>/<repo>.git" error: failed to push some refs to '/<path>/<to>/<org>/<repo>.git'
When calling the defective PR, a message appears
This pull request is broken due to missing fork information.
I've run the following tasks trying to fix it the issue:
There actually were no manual steps I did to modify the repo.
Edit (16 July 2021)
So, reproduced the issue and checked the logs in
dev
mode and with log leveltrace
.The following logs have been written:
Note: User, organisation, repo names and repo directory have been exchanged by
myuser
,myorganisation/myrepo
and/path/to/repos
Frontend
Backend
See gitea.log
Edit 2 (16 July 2021)
The project exists and is a git repo.
After using the config parameters from the comments the following got printed to the console:
console.log
The only thing I've sanitized are organisation name, repo name and IP address (CSFR token also)
I've preserved its integrity.
By the way, after getting this error, a new pull request will be created and displayed like this:

I can only create a new PR for both branches
develop
->master
when the defect one is closed.Screenshots
The text was updated successfully, but these errors were encountered: