[jbosstools-issues] [JBoss JIRA] (JBIDE-12150) Git repository is sometimes corrupted after application creation

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12150: ------------------------------------- Steps to Reproduce: 1) EXEC: launch the *New OpenShift Application* wizard and create a new OpenShift application that you import to your workspace. (ex. call the applicatino *as*) 2) ASSERT: Your application gets imported to your workspace (ex. project *as*) 3) EXEC: delete the new project, kill the OpenShift application 4) EXEC: create the very same application again and have it imported to your workspace 5) EXEC: Go to the *Git Perspective* and double click some file, so that it gets opened in a editor. You'll very soon get the following error: !MissingObjectException.png! 6) EXEC: Go to the command-line and do *git fsck*. You'll spot something very similar to this: {code} [adietish@adietish-thinkpad as2]$ git fsck broken link from commit 6410005677d35ea202df51097c4077f36d8b9ac1 to tree 0a2127cf741ef75aa1d807ad8931366cf63fc579 missing tree 0a2127cf741ef75aa1d807ad8931366cf63fc579 missing blob ef669b78c38fa1317bc89d5d93cd3205c615130f {code} Interesting enough, .gitignore is now a *new* file in the git repo even though this is completely erroneous. .gitignore was cloned, we only modified it by adding some further entries (.settings, .classpath, .project, etc.): {code} [adietish@adietish-thinkpad as2]$ git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. # # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: .gitignore {code} ALTERNATIVE: 1) EXEC: launch the *New OpenShift Application* wizard and create a new OpenShift application that you import to your workspace. (ex. call the applicatino *as*) 2) ASSERT: Your application gets imported to your workspace (ex. project *as*) 3) EXEC: delete the new project 4) EXEC: Reimport the application from OpenShift to your workspace 6) EXEC: Go to the command-line and do *git fsck*. You'll spot something very similar to this: {code} git fsck broken link from commit 74682dc05a4085a4165ef1a280129e9a9c5d412f to tree 9b742cf75471e6505b5ce7272104f34064326194 missing tree 9b742cf75471e6505b5ce7272104f34064326194 missing blob ef669b78c38fa1317bc89d5d93cd3205c615130f {code} was: 1) EXEC: launch the *New OpenShift Application* wizard and create a new OpenShift application that you import to your workspace. (ex. call the applicatino *as*) 2) ASSERT: Your application gets imported to your workspace (ex. project *as*) 3) EXEC: delete the new project, kill the OpenShift application 4) EXEC: create the very same application again and have it imported to your workspace 5) EXEC: Go to the *Git Perspective* and double click some file, so that it gets opened in a editor. You'll very soon get the following error: !MissingObjectException.png! 6) EXEC: Go to the command-line and do *git fsck*. You'll spot something very similar to this: {code} [adietish@adietish-thinkpad as2]$ git fsck broken link from commit 6410005677d35ea202df51097c4077f36d8b9ac1 to tree 0a2127cf741ef75aa1d807ad8931366cf63fc579 missing tree 0a2127cf741ef75aa1d807ad8931366cf63fc579 missing blob ef669b78c38fa1317bc89d5d93cd3205c615130f {code} Interesting enough, .gitignore is now a *new* file in the git repo even though this is completely erroneous. .gitignore was cloned, we only modified it by adding some further entries (.settings, .classpath, .project, etc.): {code} [adietish@adietish-thinkpad as2]$ git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. # # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: .gitignore {code} ALTERNATIVE: 1) EXEC: launch the *New OpenShift Application* wizard and create a new OpenShift application that you import to your workspace. (ex. call the applicatino *as*) 2) ASSERT: Your application gets imported to your workspace (ex. project *as*) 3) EXEC: delete the new project 4) EXEC: Reimport the application from OpenShift to your workspace 6) EXEC: Go to the command-line and do *git fsck*. You'll spot something very similar to this: {code} git fsck broken link from commit 74682dc05a4085a4165ef1a280129e9a9c5d412f to tree 9b742cf75471e6505b5ce7272104f34064326194 missing tree 9b742cf75471e6505b5ce7272104f34064326194 missing blob ef669b78c38fa1317bc89d5d93cd3205c615130f {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira