[BUG] LFS pull fails on a migrated repo in Gitea

[deniscep]

• Open VM Jumpbox
• Install Git client from git-scm.com
• Open Gitea and migrate a repo (e.g. https://github.com/microsoft/InnerEye-DeepLearning/) with LFS enabled.
• From git bash, do git clone, git lfs install, git lfs pull -> Gitea responds with 404

As an investigation step, I'd recommend setting up a stand-alone Gitea and verifying that LFS actually works as this feature has been added fairly recently.

[guybartal]

Managed to reproduce 404 locally in stand-alone Gitea

[guybartal]

I think something doesn't work well on the migration of an existing repository with lfs tracked files,
when I test it locally with a new repository I've managed to track, push, and pull a large file, and I also can see it in the lfs path inside the container.
comparing migrated lfs tracked file with original github repo, it looks like this:

[guybartal]

Looks like it's an open issue:
go-gitea/gitea#16935

[deniscep]

Thanks and great job @guybartal on researching this! Let's then also raise our findings with Gitea and track the issue from that side. For now, we'll have to live without LFS; let's see if we can get InnerEye tests running without it, or do we need to ask MSR to update their repo.

[adishachar]

great research @guybartal , adding @marrobi @Lybecker

[Lybecker]

Great work @guybartal! Thank you :)

[christoferlof]

Moving off the board for the time being as we're blocked on Gitea issue 16935.
go-gitea/gitea#16935

[marrobi]

@chboudry have you seen this when working on Inner Eye at all?

[marrobi]

Closing as this is an issue with Gitea and not aware of anybody being blocked by it.