Maybe it's a mix of pushing to the ASF repository and Github mirrors? I'm only pushing to the ASF repositories (although not that frequently anymore...).
Cheers, Fabian Am Di., 24. Sept. 2019 um 10:50 Uhr schrieb Till Rohrmann < trohrm...@apache.org>: > Pushing directly to Github also works for me without a problem. > > Cheers, > Till > > On Tue, Sep 24, 2019 at 10:28 AM Jark Wu <imj...@gmail.com> wrote: > > > Hi Bowen, > > > > I have also encountered this problem. I don't know how to fix this. > > But pushing to GitHub repo always works for me. > > > > Best, > > Jark > > > > On Tue, 24 Sep 2019 at 06:05, Bowen Li <bowenl...@gmail.com> wrote: > > > > > Hi committers, > > > > > > Recently I've run a repo issue multiple times in different days. When I > > > tried to push a commit to master, git reports the following error: > > > > > > ``` > > > remote: This repository has been locked due to synchronization issues: > > > remote: - /x1/gitbox/broken/flink.txt exists due to a previous error, > > and > > > prevents pushes. > > > remote: This could either be a benign issue, or the repositories could > be > > > out of sync. > > > remote: Please contact us...@infra.apache.org to have infrastructure > > > resolve the issue. > > > remote: > > > To https://gitbox.apache.org/repos/asf/flink.git > > > ! [remote rejected] master -> master (pre-receive hook declined) > > > error: failed to push some refs to ' > > > https://gitbox.apache.org/repos/asf/flink.git' > > > ``` > > > > > > This is quite a new issue that didn't come till two or three weeks > ago. I > > > researched online with no luck. I also reported it to ASF INFRA [1] but > > > their suggested solution doesn't work. > > > > > > The issue however usually goes away the next morning in PST, so I > assume > > > someone from a different timezone in Asia or Europe fixes it somehow? > Has > > > anyone run into it before? How did you fix it? > > > > > > Thanks, > > > Bowen > > > > > > [1] https://issues.apache.org/jira/projects/INFRA/issues/INFRA-18992 > > > > > >
