Bug 420680

Description Anthony Hunter 2013-10-29 18:02:56 EDT

Created attachment 237048 [details]
Screen shot of the problem

Start the server using the simple metadata storage and clone a Git repository using ssh, as in ssh://ahunter@git.eclipse.org/gitroot/orion/org.eclipse.orion.client.git

If you have never accessed git.eclipse.org before, the browser will prompt you to add the ssh-rsa key for the host. You will also be prompted a second time for your git password.

After completion, you will be left with three projects, org.eclipse.orion.client, org.eclipse.orion.client-1 and org.eclipse.orion.client-2 , see the attached screenshot.

org.eclipse.orion.client-2 actually works correctly, the other two projects are broken.

If you type your password wrong and/or cancel and repeat the process, you will get even more org.eclipse.orion.client-X projects.

This problem does not occur with the default legacy metastore.

This problem does not occur if you use https for the Git clone URL.

The Git clone handler on the server creates the project, does a Git init and then deletes the project at the end when it figures out it has insufficient information from the user. The Orion client does multiple POSTs depending on how many additional times you are prompted. As a result of bug 420679, the old project contents created by the Git init that should have been deleted on the server are left around and then they spontaneously reappear when it tries to create a project the second time with the same name. The Git clone handler works around this conflict by using a different project by appending a number "-1", but the old project still reappears.

This problem will be fixed by resolving bug 420679 and Bug 420677.