gitea: Pushing to empty repository is not reflected in web UI

Gitea version (or commit ref): 1.10.2
Git version: 2.25.0
Operating system: ArchLinuxARM
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No: https://try.gitea.io/mxt92822/empty_test
- Not relevant
Log gist: https://gist.github.com/kauron/136587e6abf7611481d7461000eb8c4d

Description

Exactly the same as in #9365, but the filesystem is mounted with exec. I think the localhost API calls are the hooks, but I’m not sure. The hooks in the repo run properly when executed manually through the terminal.

(description copied from the previously mentioned issue)

I created a new repo and pushed a local repository. I tried it both with --all (it has two branches) and without (pushed only master). Either way the repository is not changed to non-empty. I did it manually in the DB to set the is_empty column to 0 which fixed the problem.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 84 (39 by maintainers)

Commits related to this issue

Tolerate a terminal CR on a pre/post-receive line My suspicion is that occasionally windows users will send a terminal CRLF on the post-receive lines in violation of the git spec. Currently gitea enf... — committed to zeripath/gitea by zeripath 4 years ago
Fix https://github.com/go-gitea/gitea/issues/9792 git-svn-id: file:///srv/repos/svn-community/svn@705150 9fca08f4-af9d-4005-b8df-a31f2cc04f65 — committed to archlinux/svntogit-community by ArchangeGabriel 4 years ago
Fix https://github.com/go-gitea/gitea/issues/9792 git-svn-id: file:///srv/repos/svn-community/svn@705150 9fca08f4-af9d-4005-b8df-a31f2cc04f65 — committed to archlinux/svntogit-community by ArchangeGabriel 4 years ago

Most upvoted comments

Great, looks like everything’s implemented. The Wiki’s been updated, too 👍

ltguillaume on Sep 14, 2020

Thanks @ItGuillaume really sorry this took so long

zeripath on Sep 11, 2020

The following addition to the Arch Wiki has solved the following issues for me:

Newly created repos remain as if empty in web UI after pushing commits
Repo sizes remain 0B after manually setting repos those as non-empty
No repo updates on the Dashboard (https://github.com/go-gitea/gitea/issues/6620)

User Simplefied has added this workaround on June 6th (https://wiki.archlinux.org/index.php?title=Gitea&type=revision&diff=618524&oldid=615095).

Process dumped core on ArchLinux ARM

A problem can appear after pushing new repo. In web UI repo stay uninitialized, and the following error is present in the system journal:
Jun 06 14:34:20 rpi-srv systemd-coredump[5724]: Process 5722 (cat) of user 986 dumped core.
                                                Stack trace of thread 5722:
                                                #0  0x0000000076f06e58 posix_fadvise64 (libc.so.6 + 0xd2e58)
To fix this problem, override gitea.service: # systemctl edit gitea
[Service]
SystemCallArchitectures=
SystemCallFilter=

ltguillaume on Sep 11, 2020

This issue still hasn’t been addressed and basically means I have to do a manual SQL queryy every time I create a new repo.

ltguillaume on Jul 29, 2020

OK so those are all appropriately executable, next could you check the contents and mode of pre-receive.d/gitea

To update/correct these you need to use the administrator task “Update and resynchronize hooks”

zeripath on Jan 16, 2020