github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

git lfs mirror download request maybe shouldn't carry Accept #13074

New Issue
Closed
opened 2025-11-02 10:29:29 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 10:29:29 -06:00
Owner
Copy Link

Originally created by @Zoupers on GitHub (May 30, 2024).

Description

My situation is as follows: I use Gitea to mirror a repository on Bitbucket. Then, I found that the content stored using LFS (Large File Storage) was not correctly synchronized. So, I opened the trace logs to check. The batch operation was normal, but when it came to the download operation, the first server directly returned a 500 error, and no response body was returned. Therefore, I tried to understand what was happening from the source code and found that the request header for the download operation would additionally include an Accept field. When I removed it, the download worked properly...

Followed by the official doc, it seems there is no need to download with Accept header, maybe we can remove it from download?

I don't have the permission to the bitbucket server, so I don't know what happend in the bitbucket background.

Gitea Version

v1.22.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

linux

How are you running Gitea?

run from docker

Database

None

Originally created by @Zoupers on GitHub (May 30, 2024). ### Description My situation is as follows: I use Gitea to mirror a repository on Bitbucket. Then, I found that the content stored using LFS (Large File Storage) was not correctly synchronized. So, I opened the trace logs to check. The batch operation was normal, but when it came to the download operation, the first server directly returned a 500 error, and no response body was returned. Therefore, I tried to understand what was happening from the source code and found that the request header for the download operation would additionally include an Accept field. When I removed it, the download worked properly... Followed by the official [doc](https://github.com/git-lfs/git-lfs/blob/main/docs/api/basic-transfers.md), it seems there is no need to download with `Accept` header, maybe we can remove it from download? I don't have the permission to the bitbucket server, so I don't know what happend in the bitbucket background. ### Gitea Version v1.22.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System linux ### How are you running Gitea? run from docker ### Database None
GiteaMirror added the topic/lfstype/bug labels 2025-11-02 10:29:29 -06:00
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 topic/lfs 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#13074
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?