Is there an issue syncing repositories that are forks from repos in a different workspace?

[tdentremont3]

We have a few repos that are forks of each other, 3 of them are in one workspace the 4th is a local development fork kept in a personal workspace. So our local dev repos are forks of our Dev repo, our Dev repo is a fork of our QA repo, and our QA repo is a fork of our Production repo. 
Just recently, we've noticed that it takes a very long time to sync our local dev repos from the main Dev repo, but to sync from Prod to QA and QA to Dev, work fine. 

We need to do have the sync work from our Dev repo down to our local repos. Is there a problem syncing between workspaces?

[Patrik S]

Hello @tdentremont3 and thank you for reaching out to Community!

As synching the fork with the upstream repos involves a merging operation, the time it would take depends on the number of commits the fork is behind and the number of changes in each commit. The fact they are in separate workspaces shouldn't have an influence on the time it takes to complete.

Could you please confirm how many commits the fork was behind when you executed the sync operation? 

Also, when you say it takes a very long time to sync, could you share the average time it takes to complete the sync from dev to local and compare it with qa to dev (or prod to qa) ? How long did it use to take in the past?  This is so we can get an order of magnitude.

Thank you, @tdentremont3 !
Patrik S

[tdentremont3]

Thanks for the reply. In our case, the number of commits were minimal and the number of changes per commit were also minimal. Also, in each case each repo was only a few commits behind the other. For example, my local was 6 commits behind, whereas Dev was 4 commits behind QA. Not very much.
We did finally manage to get our repos all synced up eventually. 

It was taking over an hour in some cases to sync between Dev and local, but between QA and Dev, it was just minutes or less. 

Thanks.

Terry.

[Patrik S]

Hey @tdentremont3 ,

Thank you for the confirmation. Indeed 1 hour is a long period for a sync to complete.

If you noticed this just happened during a short period in the past, and it's working fine in your latest syncs, it might have been a temporary hiccup in the platform.

However, if you are seeing this delay (> 1 hour to sync) to be consistent across multiple syncs in the last few weeks, please let me know as we might need to create an internal ticket for you to investigate this further.

Thank you, @tdentremont3 !

Patrik S