Open earlbread opened 3 weeks ago
Which version did you try to upgrade from?
Which version did you try to upgrade from?
The previous version is 0.58.1 @ikhoon
I'm looking into it now, but I suspect there may be a bug in jGit itself.
However, I am not sure of the clear difference between success and failure in some cases.
I have no idea at the moment. @earlbread Does this happen always even if you restart the replicas?
@minwoox We are running central dogma in two different environments, alpha and prod, and the same thing is happening in both alpha and prod. 🤔
First, let's try restarting in alpha environment.
Could you create a new mirror config? I want to know if it doesn't work even when a new git repository is created, or if the problem only occurs when upgrading.
Not every git repo has a mirror problem. We are experiencing this issue for a specific git repo.
After restarting, the repos are still experiencing the same issue. @minwoox
as far as I know,
https://github.com/line/centraldogma/pull/808
I know that the shallow feature was added in this commit. (FetchCommand). The error did not occur in previous versions before shallow was added.
If #808 was the cause, you can delete _mirrors
directory as a workaround. The folder will be created automatically if absent.
@ikhoon
ok, let’s delete the _mirrors
directory and restart.
In addition to the workaround, we will handle this issue separately.
The errors are disappeared after deleting _mirrors
. Thank you! @ikhoon
Glad to hear. /metadata.json
is located in meta
folder which should not be affected by _mirrors
removal.
It seems that there was a conflict with garbage data in the _mirrors
directory in past versions of central dogma.
It works normally now! Thank your support!
Glad to hear.
/metadata.json
is located inmeta
folder which should not be affected by_mirrors
removal.
It was my mistake. I copied _mirrors
after creating the /data/tmp
directory, and I think that's what caused the problem. I deleted /data/tmp
and backed up the data to /data/_tmp
and the problem did not occur. Thank you!
Hi team. After upgrading to 0.66.0, I am getting the following error message. This issue seems to be preventing mirroring from working properly. Do you have any idea what is causing the issue and is there anything I can try to fix it?
Thank you.