gitea: Unable to push to an existing repo after upgrade to 1.0.0+294-g04fdeb9d (on Postgres 9.6)
- Gitea version (or commit ref): 1.0.0+294-g04fdeb9d
- Git version: gitea/gitea:latest (image ID: e603f1ca59e2)
- Operating system: gitea/gitea:latest (image ID: e603f1ca59e2)
- Database (use
[x]):- PostgreSQL: postgres:9.6 (image ID: ecd991538a0f)
- MySQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist: https://gist.github.com/bkleef/f51421543d17b2ee18db0fdc5e2ba167
Description
After pulling latest gitea Docker image we are unable to push to an existing and new repo. Reverting back to gitea/gitea:1.0.1 fixes this. We use internal SSH-Server provided by Gitea.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 23 (14 by maintainers)
@bkleef @jomp16 Please confirm this is resolved by #1007
Found where the problem is. You have to put more than 1 log mode in your config file except console.
Gitea version: 1.0.0+300-gfd941db2.
This also happens with MySQL.
HTTP(s):
SSH:
Reverting commits: 70ae6d197b28f018264798b07a16bf3acc36405c and 04fdeb9d8d4dc3cf296d8354ee29f1d053154a54 makes it work again.
I’m not sure why it works on try.gitea.io and not on my side. The only difference the database engine is MySQL (MariaDB to be more exact) on my side instead of SQLite on your side.
You should update to 70ae6d197b28f018264798b07a16bf3acc36405c not ffde33bdfabceb69ac2bdf43466cc0508fec0add and then test it.
@bkleef please help to confirm #993 fix this.