forgejo/modules/lfs
Royce Remer 45181ee945
Support legacy _links LFS batch responses (#31513)
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 the `actions` field. When Gitea must fallback to the legacy
`_links` field a logline is emitted at INFO level which looks like this:
```
...s/lfs/http_client.go:188:performOperation() [I] <LFSPointer ee95d0a27ccdfc7c12516d4f80dcf144a5eaf10d0461d282a7206390635cdbee:160> is using a deprecated batch schema response!
```

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 modern `actions`).

Signed-off-by: Royce Remer <royceremer@gmail.com>
(cherry picked from commit df805d6ed0458dbec258d115238fde794ed4d0ce)
2024-06-29 07:56:18 +02:00
..
client.go
client_test.go
content_store.go [GITEA] Drop sha256-simd in favor of stdlib 2024-02-05 16:09:40 +01:00
endpoint.go
endpoint_test.go
filesystem_client.go fix: close file in the Upload func (#30262) 2024-04-07 15:40:31 +02:00
http_client.go Support legacy _links LFS batch responses (#31513) 2024-06-29 07:56:18 +02:00
http_client_test.go Support legacy _links LFS batch responses (#31513) 2024-06-29 07:56:18 +02:00
LICENSE
pointer.go [GITEA] Drop sha256-simd in favor of stdlib 2024-02-05 16:09:40 +01:00
pointer_scanner_gogit.go
pointer_scanner_nogogit.go
pointer_test.go
shared.go Support legacy _links LFS batch responses (#31513) 2024-06-29 07:56:18 +02:00
transferadapter.go Fix #31185 try fix lfs download from bitbucket failed (#31201) 2024-06-16 13:42:59 +02:00
transferadapter_test.go Fix #31185 try fix lfs download from bitbucket failed (#31201) 2024-06-16 13:42:59 +02:00