Skip to content
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

All LFS files got empty (no more Stored with Git LFS) after Gitea WebUI file editing and commit #4778

Closed
2 of 7 tasks
lanterna72 opened this issue Aug 23, 2018 · 0 comments · Fixed by #5702
Closed
2 of 7 tasks
Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug

Comments

@lanterna72
Copy link

lanterna72 commented Aug 23, 2018

  • Gitea version (or commit ref): 1.5
  • Git version: 2.18.0
  • Operating system: Windows Server 2016 Standard
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL (SqlServer 2016 Standard Edition)
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (because gitlfs is not enabled)
    • Not relevant
  • Log gist:

config file has gitlfs enabled

...
LFS_START_SERVER = true
LFS_CONTENT_PATH = C:/gitea/data/lfs
LFS_JWT_SECRET = <<token>>
...

Description

Phase 1 - 1st commit

I do have a project with a markdown file in the root folder and a folder named 'lfs_files' where there are .png and .pdf files.

before 1st commit I enabled LFS and tracked png and pdf files as in the git lfs tutorial https://git-lfs.github.com

git lfs track "*.pdf"
git lfs track "*.png"
git add .gitattributes

I do the 1st commit and 1st pull, all ok, accessing the WebUI I see all files are committed and all LFS tracked files reports the correct size and label (Stored with Git LFS)

image

image

Phase 2 - Edit markdown file under gitea webui

I edit the index.md directly in the gitea webui and commit clicking on commit changes button

image

From now on all LFS files has 0 size and (Stored with Git LFS) is disappeared.

image

I tried with multiple repositories, simple or more complex all led to the same result.

@lunny lunny added the type/bug label Aug 24, 2018
@lafriks lafriks added the issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP label Aug 24, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants