1
0
Fork 0
gitea/modules/packages
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
..
composer
conan
container
helm Replace yaml.v2 with yaml.v3 (#21832) 2022-11-21 16:36:59 +08:00
maven
npm
nuget
pub Replace yaml.v2 with yaml.v3 (#21832) 2022-11-21 16:36:59 +08:00
pypi
rubygems Replace yaml.v2 with yaml.v3 (#21832) 2022-11-21 16:36:59 +08:00
vagrant
content_store.go Workaround for container registry push/pull errors (#21862) 2022-11-25 13:47:46 +08:00
hashed_buffer.go
hashed_buffer_test.go
multi_hasher.go
multi_hasher_test.go