I have a module that has recently been promoted from sandbox to full project.

https://drupal.org/project/achecker_integration

I was expecting the git url to change once this was done, but the sandbox url is still listed in the version control tab https://drupal.org/project/achecker_integration/git-instructions (which no longer works: "fatal: remote error: Repository does not exist. Verify that your remote is correct.")

git clone git.drupal.org:project/2146633.git

I extrapolated to what i though it should now be:

git clone git.drupal.org:project/achecker_integration.git

but this doesnt work either (same error).

Also, the commit links to to drupalcode.org (https://drupal.org/node/2146633/commits) are now broken.

Am I missing something here or has something bad happened?

Thanks

Andy

Comments

helmo’s picture

Issue summary: View changes

This is definitely not supposed to happen...

I've setup some debug output on:
http://projectname-drupal.redesign.devdrupal.org/project/achecker_integr...

This tells me that the VersioncontrolGitRepository Object has a [name] => 2146633 property ... :(

marvil07’s picture

Issue summary: View changes

This sounds a lot like #2124975: Wrong project name in the New URL, can we make sure project weights are ok? (see comment 7 and 10)

helmo’s picture

The weights on projectname-drupal.redesign.devdrupal.org/ are the same as in https://drupal.org/comment/8280141#comment-8280141

[projectname_drup]> select name, weight from system where name in ('project_git_instructions', 'drupalorg_versioncontrol');
+--------------------------+--------+
| name                     | weight |
+--------------------------+--------+
| drupalorg_versioncontrol |     15 |
| project_git_instructions |     16 |
+--------------------------+--------+
2 rows in set (0.00 sec)
andystone78’s picture

Hi

Is this likely to be fixed soon? As it stands i cannot make any changes to the module so i am considering abandoning it and recreate using a different name. I would rather not do this but i cant really see another option?

Kind regards

Andy

helmo’s picture

Project: Git on Drupal.org » Drupal.org site moderators
Component: Git » Project/Git problem

Moving to the webmasters queue to get some more eyes on this.

marvil07’s picture

Not sure what had happened, it seems like the enqueued job to do the repository migration(see drupalorg_versioncontrol_project_promote_sandbox()) failed, was removed or was never executed.
Can we grep for Failed to enqueue promotion of sandbox in watchdog logs?

The git repository itself is still on the sandbox path.

The way to fix this will be to run that hook manually, preparing the project node accordingly if needed, i.e. to be the string name instead of the nid.

Pending to test the solution on git7site.

drumm’s picture

This affects 3 projects:

mysql> SELECT vcpp.nid, vcr.root FROM versioncontrol_project_projects vcpp INNER JOIN versioncontrol_repositories vcr ON vcr.repo_id = vcpp.repo_id AND root LIKE '/var/git/repositories/sandbox/%' INNER JOIN field_data_field_project_type fdfpt ON fdfpt.entity_id = vcpp.nid AND fdfpt.field_project_type_value = 'full';
+---------+-------------------------------------------------------+
| nid     | root                                                  |
+---------+-------------------------------------------------------+
| 1126680 | /var/git/repositories/sandbox/dman/1126680.git        |
| 2146633 | /var/git/repositories/sandbox/andystone78/2146633.git |
| 2161871 | /var/git/repositories/sandbox/xcf33/2161871.git       |
drumm’s picture

Assigned: Unassigned » drumm
Status: Active » Fixed

Now all fixed. drupalorg_versioncontrol_project_promote_sandbox(node_load(2146633)). util occasionally gets overloaded, so the process probably got killed or something.

andystone78’s picture

Status: Fixed » Closed (fixed)

Excellent,

Thanks all

Andy