Skip to content
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

500 error creating pull request for LFS repo #4760

Closed
2 of 7 tasks
DarkMorford opened this issue Aug 21, 2018 · 8 comments
Closed
2 of 7 tasks

500 error creating pull request for LFS repo #4760

DarkMorford opened this issue Aug 21, 2018 · 8 comments
Labels
issue/duplicate The issue has already been reported. type/bug

Comments

@DarkMorford
Copy link

  • Gitea version (or commit ref): 1.5.0
  • Git version: 2.18.0.windows.1
  • Operating system: Windows Server 2016
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

Creating a pull request on a repository that uses LFS produces a 500 error.

Relevant log snippet:

2018/08/21 10:19:06 [...routers/repo/pull.go:839 CompareAndPullRequestPost()] [E] PushToBaseRepo: Push: exit status 1 - batch request: missing protocol: "G:\\GitRepos\\storageteam\\qualificationtools.git/info/lfs"
error: failed to push some refs to 'G:\GitRepos\storageteam\qualificationtools.git'
@Akcaxup
Copy link

Akcaxup commented Aug 21, 2018

Pull Request is not created if assigned participant in this moment.

@lafriks
Copy link
Member

lafriks commented Aug 21, 2018

I think there was already issue reported about this

@lunny
Copy link
Member

lunny commented Aug 22, 2018

related with #4463, but that issue is merging issue not creating.

@stale
Copy link

stale bot commented Jan 13, 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 stale bot added the issue/stale label Jan 13, 2019
@iCodeSometime
Copy link

This is happening for me as well

@stale stale bot removed the issue/stale label Jan 24, 2019
@stale
Copy link

stale bot commented Mar 25, 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 stale bot added the issue/stale label Mar 25, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Mar 26, 2019
@zeripath
Copy link
Contributor

I think I've finally found the cause and a workaround:

I suspect that you have git-lfs version greater than 2.3.4 installed on your server and gitea user has a .gitconfig file containing:

[filter "lfs"]
	clean = git-lfs clean -- %f
	smudge = git-lfs smudge -- %f
	process = git-lfs filter-process
	required = true

If you remove that that should act as a workaround.

@zeripath zeripath added issue/duplicate The issue has already been reported. and removed issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented labels May 27, 2019
@zeripath
Copy link
Contributor

This is a duplicate of #732

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported. type/bug
Projects
None yet
Development

No branches or pull requests

6 participants