-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Error 500 when creating pull request #6460
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
Comments
What version of git are you using? https://stackoverflow.com/questions/50093771/git-clone-warning-failed-to-restrict-file-handles |
Git version is 2.16.2.windows.1 |
Now I have different error: 2019/03/29 09:39:15 [...routers/repo/pull.go:912 CompareAndPullRequestPost()] [E] PushToBaseRepo: Push: exit status 1 - error: cannot spawn hooks/pre-push: No such file or directory |
I think you need to Regenerate hooks from the admin panel on Gitea |
I tried to regenerate hooks from command line (gitea admin regenerate hooks), but it didn't make any difference. I still get the same error. |
pre-push is a client hook: I guess for the the obvious first -- does the pre-push hook exist in this repo locally and seem OK? If so, is sh.exe in your PATH? I think on newer versions of git for windows it is in |
pre-push file on gitea server was empty so i removed it and successfully created new pull request . On my local pc pre-push file is not empty, but has this code:
|
OK great, and interesting. Gitea itself doesn't create/manage/add You might have a global pre-push hook on the server that is empty? That would get added to any new repos created by gitea, including when doing temporary clones for various tasks. Is it possible to check that? Perhaps the server user has git-lfs installed and it generated an empty hook somehow -- though again that isn't anything gitea itself manages. I've never used Windows or git-lfs so not very helpful beyond that :( If it repeats itself, I'd bet one of the two things above is the cause. As for the local hook, presumably you need that or don't depending on git lfs use (as it says). |
Only this project has pre-push hook, other project are without pre-push hook. On the project without pre-push hook creating pull request is working ok. Server has git-lfs installed, could this be a problem? |
@bkodre It wouldn't be possible for anyone here to be sure how that empty hook file got there, the above suggestions are just possibilities that you or your server/git administrator could look into if it is a reoccurring problem. In any case, it doesn't appear to be an issue with Gitea itself here but glad the particular issue with using Gitea was fixed. |
Deleting pre-push solved issue for me so i will close this issue. Thanks for your help. |
Description
2019/03/28 13:21:58 [...routers/repo/pull.go:912 CompareAndPullRequestPost()] [E] PushToBaseRepo: Push: exit status 1 - warning: failed to restrict file handles (2)
The text was updated successfully, but these errors were encountered: