forgejo-federation/tests
KN4CK3R a1ae83f36e
Workaround for container registry push/pull errors (#21862)
This PR addresses #19586

I added a mutex to the upload version creation which will prevent the
push errors when two requests try to create these database entries. I'm
not sure if this should be the final solution for this problem.

I added a workaround to allow a reupload of missing blobs. Normally a
reupload is skipped because the database knows the blob is already
present. The workaround checks if the blob exists on the file system.
This should not be needed anymore with the above fix so I marked this
code to be removed with Gitea v1.20.

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2022-11-25 13:47:46 +08:00
..
e2e Better repo API unit checks (#21130) 2022-09-28 00:23:58 +02:00
gitea-repositories-meta Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
integration Workaround for container registry push/pull errors (#21862) 2022-11-25 13:47:46 +08:00
mssql.ini.tmpl Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
mysql.ini.tmpl Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
mysql8.ini.tmpl Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
pgsql.ini.tmpl Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
sqlite.ini.tmpl Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
test_utils.go Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
testlogger.go Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00