You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR
- Fix#26093. Replace `time.Time` with `timeutil.TimeStamp`
- Fix#26135. Add missing `xorm:"extends"` to `CountLFSMetaObject` for
LFS meta object query
- Add a unit test for LFS meta object garbage collection
This PR
- Fixgo-gitea#26093. Replace `time.Time` with `timeutil.TimeStamp`
- Fixgo-gitea#26135. Add missing `xorm:"extends"` to `CountLFSMetaObject` for
LFS meta object query
- Add a unit test for LFS meta object garbage collection
Backport #26122 by @Zettat123
This PR
- Fix#26093. Replace `time.Time` with `timeutil.TimeStamp`
- Fix#26135. Add missing `xorm:"extends"` to `CountLFSMetaObject` for
LFS meta object query
- Add a unit test for LFS meta object garbage collection
Co-authored-by: Zettat123 <[email protected]>
Description
The cron job to garbage collect LFS fails.
Steps to reproduce:
docker run -d --name gitea -p 8081:3000 -e GITEA__server__LFS_START_SERVER=true -e GITEA__security__INSTALL_LOCK=true -e GITEA__log__LEVEL=debug -e GITEA__server__ROOT_URL=http://0.0.0.0:8081/ gitea/gitea:1.20 bash -c '/bin/s6-svscan /etc/s6 & sleep 10 ; su -c "gitea admin user create --admin --username root --password admin1234 --email [email protected]" git && sleep infinity'
Gitea Version
v1.20.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
docker run -d --name gitea -p 8081:3000 -e GITEA__server__LFS_START_SERVER=true -e GITEA__security__INSTALL_LOCK=true -e GITEA__log__LEVEL=debug -e GITEA__server__ROOT_URL=http://0.0.0.0:8081/ gitea/gitea:1.20 bash -c '/bin/s6-svscan /etc/s6 & sleep 10 ; su -c "gitea admin user create --admin --username root --password admin1234 --email [email protected]" git && sleep infinity'
Database
SQLite
Related
The text was updated successfully, but these errors were encountered: