github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

500 error creating pull request for LFS repo #2227

New Issue
Closed
opened 2025-11-02 04:28:25 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 04:28:25 -06:00
Owner
Copy Link

Originally created by @DarkMorford on GitHub (Aug 21, 2018).

  • 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'
Originally created by @DarkMorford on GitHub (Aug 21, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - 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 - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] 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'
GiteaMirror added the type/bugissue/duplicate labels 2025-11-02 04:28:25 -06:00
GiteaMirror commented 2025-11-02 04:28:28 -06:00
Author
Owner
Copy Link

@Akcaxup commented on GitHub (Aug 21, 2018):

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

@Akcaxup commented on GitHub (Aug 21, 2018): Pull Request is not created if assigned participant in this moment.
GiteaMirror commented 2025-11-02 04:28:29 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 21, 2018):

I think there was already issue reported about this

@lafriks commented on GitHub (Aug 21, 2018): I think there was already issue reported about this
GiteaMirror commented 2025-11-02 04:28:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 22, 2018):

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

@lunny commented on GitHub (Aug 22, 2018): related with #4463, but that issue is merging issue not creating.
GiteaMirror commented 2025-11-02 04:28:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.
GiteaMirror commented 2025-11-02 04:28:30 -06:00
Author
Owner
Copy Link

@iCodeSometime commented on GitHub (Jan 24, 2019):

This is happening for me as well

@iCodeSometime commented on GitHub (Jan 24, 2019): This is happening for me as well
GiteaMirror commented 2025-11-02 04:28:30 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.
GiteaMirror commented 2025-11-02 04:28:31 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 26, 2019):

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 commented on GitHub (May 26, 2019): 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: ```ini [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.
GiteaMirror commented 2025-11-02 04:28:32 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 27, 2019):

This is a duplicate of #732

@zeripath commented on GitHub (May 27, 2019): This is a duplicate of #732
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2227
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?