Royce Remer df805d6ed0 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>
2024-06-28 08:42:57 +00:00
..
2024-06-11 18:47:45 +00:00
2024-02-25 13:32:13 +00:00
2024-06-17 06:45:12 +00:00
2024-06-17 21:22:39 +02:00
2024-04-03 02:16:46 +00:00
2024-06-24 13:26:42 +00:00
2023-12-25 20:13:18 +08:00
2024-04-22 23:55:43 +00:00
2024-02-25 13:32:13 +00:00
2023-11-03 15:21:05 +00:00
2024-06-11 18:47:45 +00:00
2024-06-19 06:32:45 +08:00
2024-06-19 06:32:45 +08:00
2024-01-12 21:50:38 +00:00