-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Support legacy _links LFS batch responses #31513
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GiteaBot
added
the
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
label
Jun 27, 2024
pull-request-size
bot
added
the
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
label
Jun 27, 2024
wxiaoguang
reviewed
Jun 28, 2024
wxiaoguang
reviewed
Jun 28, 2024
Signed-off-by: Royce Remer <royceremer@gmail.com>
rremer
force-pushed
the
main-legacy-lfs-support
branch
from
June 28, 2024 02:21
4d6ca2f
to
d58dced
Compare
thanks for the review @wxiaoguang , updated with your suggestions and force pushed |
wxiaoguang
approved these changes
Jun 28, 2024
GiteaBot
added
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
and removed
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
labels
Jun 28, 2024
lunny
reviewed
Jun 28, 2024
lunny
approved these changes
Jun 28, 2024
GiteaBot
added
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
and removed
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
labels
Jun 28, 2024
lunny
added
the
reviewed/wait-merge
This pull request is part of the merge queue. It will be merged soon.
label
Jun 28, 2024
@rremer please fix the merge conflicts. 🍵 |
GiteaBot
removed
the
reviewed/wait-merge
This pull request is part of the merge queue. It will be merged soon.
label
Jun 28, 2024
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Jul 1, 2024
* giteaofficial/main: [skip ci] Updated translations via Crowdin Fix markdown preview $$ support (go-gitea#31514) Add Passkey login support (go-gitea#31504) Use stable version of fabric (go-gitea#31526) Always use HTML attributes for avatar size (go-gitea#31509) Add initial typescript config and use it for eslint,vitest,playwright (go-gitea#31186) Support legacy _links LFS batch responses (go-gitea#31513) Fix JS error with disabled attachment and easymde (go-gitea#31511)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
modifies/go
Pull requests that update Go code
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support legacy _links LFS batch response.
Fixes #31512.
This is backwards-compatible change to the LFS client so that, upon mirroring from an upstream which has a batch api, it can download objects whether the responses contain the
_links
field or its successor theactions
field. When Gitea must fallback to the legacy_links
field a logline is emitted at INFO level which looks like this:I've only run
test-backend
with this code, but added a new test to cover this case. Additionally I have a fork with this change deployed which I've confirmed syncs LFS from Gitea<-Artifactory (which has legacy_links
) as well as from Gitea<-Gitea (which has the modernactions
).