Mirroring was fixed but now broken again #1761

cfr commented 2025年01月15日 03:05:01 +01:00

Comment

As a number of people reported in #1745 the ability to mirror a repo recently broke. This got fixed and all the queues were said to be restarted. Certainly this was true for me. Mirroring worked as it had done before the problems started.

However, I'm now getting the same issue. Nothing appears to happen when I push to the repo or to happen periodically. If I try to sync the repo manually, I get the Pushing changes to the remote https://github.com/cfr42/nfssext.git at the moment., but nothing actually seems to happen. There's no error. Either the process doesn't start or it apparently hangs.

Repo for reference: https://github.com/cfr42/nfssext.git

I don't think this can be something I've done because it worked yesterday and only failed again today. I did have a stale sync configured (a leftover from my efforts before I realised the issue was a bug when mirroring broke before), so I've deleted that, but I've not changed anything else.

### Comment As a number of people reported in #1745 the ability to mirror a repo recently broke. This got fixed and all the queues were said to be restarted. Certainly this was true for me. Mirroring worked as it had done before the problems started. However, I'm now getting the same issue. Nothing appears to happen when I push to the repo or to happen periodically. If I try to sync the repo manually, I get the `Pushing changes to the remote https://github.com/cfr42/nfssext.git at the moment.`, but nothing actually seems to happen. There's no error. Either the process doesn't start or it apparently hangs. Repo for reference: https://github.com/cfr42/nfssext.git I don't think this can be something I've done because it worked yesterday and only failed again today. I did have a stale sync configured (a leftover from my efforts before I realised the issue was a bug when mirroring broke before), so I've deleted that, but I've not changed anything else.

Gusted commented 2025年01月17日 00:02:32 +01:00

Same issue as last time, queues are completely stuck and are processing some item indefinitely and increasing workers is not having any effect. We are looking into it.

Same issue as last time, queues are completely stuck and are processing some item indefinitely and increasing workers is not having any effect. We are looking into it.

thefossguy commented 2025年01月23日 10:18:37 +01:00

A ping for people subscribed to this issue; this seems to have been resolved, for me. You might want to try re-syncing manually.

A ping for people subscribed to this issue; this seems to have been resolved, for me. You might want to try re-syncing manually.

cfr commented 2025年01月30日 09:15:04 +01:00

@Gusted wrote in #1761 (comment):

Same issue as last time, queues are completely stuck and are processing some item indefinitely and increasing workers is not having any effect. We are looking into it.

This seems to be resolved, but I don't know if that is just chance and this should be left open or closed?

Thanks for working on it!

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/1761#issuecomment-2591267: > Same issue as last time, queues are completely stuck and are processing some item indefinitely and increasing workers is not having any effect. We are looking into it. This seems to be resolved, but I don't know if that is just chance and this should be left open or closed? Thanks for working on it!

Gusted commented 2025年01月30日 10:16:43 +01:00

Seems to have been stable the last week, we are not currently monitoring the queue anymore to see if it gets stuck. I hope it merely was an transient bug.

Seems to have been stable the last week, we are not currently monitoring the queue anymore to see if it gets stuck. I hope it merely was an transient bug.