Skip to content

Gitea in docker container doesn't display my commits #12927

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

Closed
2 of 7 tasks
xakaitetoia opened this issue Sep 23, 2020 · 4 comments
Closed
2 of 7 tasks

Gitea in docker container doesn't display my commits #12927

xakaitetoia opened this issue Sep 23, 2020 · 4 comments

Comments

@xakaitetoia
Copy link

  • Gitea version (or commit ref): docker - gitea/gitea:latest
  • Git version:
  • Operating system: Ubuntu 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Hello team,
I am using the latest gitea version in docker (gitea/gitea:latest) and when creating a repo I follow the instructions from a machine and although I succeed on creating the initial README.MD file and pushing it successfully, I do not see any update in the dashboard with my commits. See screenshot. Still remains the same page with instructions. Pulling and pushing though works fine as if there were some data. It just doesn't display any contents on the specified repo

This doesn't happen if i download the gitea:1.12 version though.

Screenshots

~/docker/gitea/test$ git push -u origin masterUsername for xxx
Password for 'x:
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 207 bytes | 207.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: . Processing 1 references
remote: Processed 1 references in total
To xxxxxx/test.git

  • [new branch] master -> master
    Branch 'master' set up to track remote branch 'master' from 'origin'.

gitea

@zeripath
Copy link
Contributor

This should only happen if the post-receive hook hasn't run.

Was this repository created on a different version of Gitea and resynchronize hooks not run?

@xakaitetoia
Copy link
Author

No I did it on a fresh host with native docker installer and just downloaded the latest gitea version. If I docker-compose down and delete all gitea images / created volumes again and specify 1.12 version in docker-compose.yml then it's working fine.

@zeripath
Copy link
Contributor

Well we will need some logs.

I can't replicate this issue.

@wxiaoguang
Copy link
Contributor

It's caused by the out-sync IsEmpty state. Has been fixed by:

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants