Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have taken a look at this, and it seems like the repository is currently locked, probably something failed during parsing. I'm based on the data I could see on git6site, where I have access to database.
There I found the repo_id: drush sql-query "select vcr.repo_id, vcr.locked from versioncontrol_repositories vcr join versioncontrol_project_projects vcp on vcr.repo_id = vcp.repo_id where vcp.nid = 1857558";, which is 47158.
Then, after increasing the php memory to 512 on drush config(do not work on normal memory limit), I run:
drush sql-cli "update versioncontrol_repositories set locked = 0 where repo_id = 47158";
drush vcapi-sync-repositories 47158
After that, I think the information is now correct (notice that git6site do not use current information).
so, someone with access to shell on prod can run those to fix it.
Comments
Comment #1
marvil07 commentedI have taken a look at this, and it seems like the repository is currently locked, probably something failed during parsing. I'm based on the data I could see on git6site, where I have access to database.
There I found the repo_id:
drush sql-query "select vcr.repo_id, vcr.locked from versioncontrol_repositories vcr join versioncontrol_project_projects vcp on vcr.repo_id = vcp.repo_id where vcp.nid = 1857558";, which is 47158.Then, after increasing the php memory to 512 on drush config(do not work on normal memory limit), I run:
After that, I think the information is now correct (notice that git6site do not use current information).
so, someone with access to shell on prod can run those to fix it.
Comment #2
killes@www.drop.org commented