Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Workaround for container registry push/pull errors (#21862) #22069

Merged
merged 1 commit into from
Dec 10, 2022
Merged

Workaround for container registry push/pull errors (#21862) #22069

merged 1 commit into from
Dec 10, 2022

Commits on Dec 8, 2022

  1. Workaround for container registry push/pull errors (go-gitea#21862) 

    This PR addresses go-gitea#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>
    @KN4CK3R @lunny
    KN4CK3R and lunny committed Dec 8, 2022
    Configuration menu
    Copy the full SHA
    ad0ee26 View commit details
    Browse the repository at this point in the history