[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12150: ------------------------------------- Description: Steps to reproduce: create myapp in tools with openshift in ~/git/myapp take the git url and clone the app into a separate directory (to simulate other changes) mkdir temp cd temp git clone ssh:<specifichost>/myapp.git/ cd myapp edit README or some other existing file git commit -m "external change" README git push <ton of output> cd ~/git/myapp git push will now fail with something like: $ git push ~/git/appmy To ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/ ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes (e.g. 'git pull') before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details. Thus when trying to publish from tools it should not let you push and it should ask you before pushing with force. After [https://issues.jboss.org/browse/JBIDE-12138] has been fixed, user is prompted with a dialog that proposes to perform a "push force". While the operation seems to execute correctly, the following error is reported in the Error Log: {code} org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of push command at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:156) at org.eclipse.egit.core.op.PushOperation.run(PushOperation.java:194) at org.jboss.tools.openshift.egit.core.EGitUtils.push(EGitUtils.java:429) at org.jboss.tools.openshift.egit.core.EGitUtils.pushForce(EGitUtils.java:418) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.commitAndPushProject(ExpressPublishMethod.java:237) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishFinish(ExpressPublishMethod.java:80) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:94) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishFinish(DelegatingServerBehavior.java:147) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:974) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.jgit.errors.TransportException: ssh://7ddb1e3809e54c969a568dd03889e90f@as-minipaas.example.com/~/git/as.git/: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:186) at org.eclipse.jgit.transport.BasePackPushConnection.push(BasePackPushConnection.java:126) at org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:141) at org.eclipse.jgit.transport.Transport.push(Transport.java:1120) at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:152) ... 14 more Caused by: org.eclipse.jgit.errors.MissingObjectException: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:126) at org.eclipse.jgit.revwalk.ObjectWalk.newTreeVisit(ObjectWalk.java:726) at org.eclipse.jgit.revwalk.ObjectWalk.nextObject(ObjectWalk.java:378) at org.eclipse.jgit.storage.pack.PackWriter.findObjectsToPack(PackWriter.java:1706) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:707) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:670) at org.eclipse.jgit.transport.BasePackPushConnection.writePack(BasePackPushConnection.java:265) at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:168) ... 18 more {code} Going back to cmdline, it seems that the git repository is corrupted: {code} $ git fsck broken link from commit 70b2d1cf4705c118e5cac62d0c754df69f09fa32 to tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e missing blob 244cfe40684de36646d426ace17041cd25605cb2 missing tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e {code} In the UI you'll see the following: The *.settings* folder is not tracked, while the *.jsdtscope* within it is added & committed: !settings-untracked-jsdtscope-committed.png! was: Steps to reproduce: create myapp in tools with openshift in ~/git/myapp take the git url and clone the app into a separate directory (to simulate other changes) mkdir temp cd temp git clone ssh:<specifichost>/myapp.git/ cd myapp edit README or some other existing file git commit -m "external change" README git push <ton of output> cd ~/git/myapp git push will now fail with something like: $ git push ~/git/appmy To ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/ ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes (e.g. 'git pull') before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details. Thus when trying to publish from tools it should not let you push and it should ask you before pushing with force. After [https://issues.jboss.org/browse/JBIDE-12138] has been fixed, user is prompted with a dialog that proposes to perform a "push force". While the operation seems to execute correctly, the following error is reported in the Error Log: {code} org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of push command at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:156) at org.eclipse.egit.core.op.PushOperation.run(PushOperation.java:194) at org.jboss.tools.openshift.egit.core.EGitUtils.push(EGitUtils.java:429) at org.jboss.tools.openshift.egit.core.EGitUtils.pushForce(EGitUtils.java:418) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.commitAndPushProject(ExpressPublishMethod.java:237) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishFinish(ExpressPublishMethod.java:80) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:94) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishFinish(DelegatingServerBehavior.java:147) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:974) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.jgit.errors.TransportException: ssh://7ddb1e3809e54c969a568dd03889e90f@as-minipaas.example.com/~/git/as.git/: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:186) at org.eclipse.jgit.transport.BasePackPushConnection.push(BasePackPushConnection.java:126) at org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:141) at org.eclipse.jgit.transport.Transport.push(Transport.java:1120) at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:152) ... 14 more Caused by: org.eclipse.jgit.errors.MissingObjectException: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:126) at org.eclipse.jgit.revwalk.ObjectWalk.newTreeVisit(ObjectWalk.java:726) at org.eclipse.jgit.revwalk.ObjectWalk.nextObject(ObjectWalk.java:378) at org.eclipse.jgit.storage.pack.PackWriter.findObjectsToPack(PackWriter.java:1706) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:707) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:670) at org.eclipse.jgit.transport.BasePackPushConnection.writePack(BasePackPushConnection.java:265) at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:168) ... 18 more {code} Going back to cmdline, it seems that the git repository is corrupted: {code} $ git fsck broken link from commit 70b2d1cf4705c118e5cac62d0c754df69f09fa32 to tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e missing blob 244cfe40684de36646d426ace17041cd25605cb2 missing tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e {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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12150: ------------------------------------------ I had a failure rate of about 50% when using the liveCD while I could create 7 new apps when using OpenShift without a single failure. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-12150. ----------------------------------- Resolution: Done Patch applied on branch and trunk -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12150: ------------------------------------------ I tried to reproduce it, and it only occurrs if you (re-)create a new application (with the very same name) on OpenShift. it does not occurr if you re-import the very same application into a new project. -- 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

[ 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! 5) 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} -- 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

[ 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} ALTERNATIVE that does not involve using OpenShift: 1) EXEC: create a new java project 2) EXEC: create a new file in it (ex. test) 3) EXEC: share this project with egit: *Team->Share Project->Git->Create->* 4) EXEC: Commit new file (test) to repo: *Team->Commit->check "test"* 6) EXEC: Go to the command-line and do *git fsck*. You'll spot something 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

[ 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*. Result: 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*. Result: 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} ALTERNATIVE that does not involve using OpenShift: 1) EXEC: create a new java project (ex. test-project) 2) EXEC: share this project with egit: *Team->Share Project->Git->Create* 3) EXEC: Commit new file (test) to repo: *Team->Commit->check ".classpath"* 4) EXEC: Delete project in Eclipse, kill Repository-Folder in File-Explorer / CLI 5) EXEC: Repeat steps 1-4 6) Go to CLI and cd to the git repo. Then do: git fsck Result: 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*. Result: 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*. Result: 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} ALTERNATIVE that does not involve using OpenShift: 1) EXEC: create a new java project (ex. test-project) 2) EXEC: create a new file in it (ex. test) 3) EXEC: share this project with egit: *Team->Share Project->Git->Create* 4) EXEC: Commit new file (test) to repo: *Team->Commit->check "test"* 5) EXEC: Delete project in Eclipse, kill Repository-Folder in File-Explorer / CLI 6) EXEC: Repeat steps 1-4 7) Go to CLI and cd to the git repo. Then do: git fsck Result: 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12150: ------------------------------------------ I tried to reproduce the issue in a unit-test, but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12150 at 8/21/12 12:49 PM: -------------------------------------------------------------------- I tried to reproduce the issue in a unit-test [corrupt-repo-test.zip], but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. was (Author: adietish): I tried to reproduce the issue in a unit-test, but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12150 at 8/21/12 12:51 PM: -------------------------------------------------------------------- I tried to reproduce the issue in a unit-test [corrup-repo-test.zip], but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. was (Author: adietish): I tried to reproduce the issue in a unit-test [JBIDE-12150^corrup-repo-test.zip], but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12150 at 8/21/12 12:52 PM: -------------------------------------------------------------------- I tried to reproduce the issue in a unit-test [corrupt repo test^corrup-repo-test.zip], but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. was (Author: adietish): I tried to reproduce the issue in a unit-test [corrup-repo-test.zip], but the corruption does not happen when running the test. There must be differences btw. running this procedure in the IDE and in my unit-test. I cant spot the difference so far. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12150: ------------------------------------------ I found the issue and proposed a fix in https://bugs.eclipse.org/bugs/show_bug.cgi?id=387617#c9. -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12150: ------------------------------------------ I pushed a fix for review to https://git.eclipse.org/r/7403 (egit gerrit) -- 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

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12150 at 8/30/12 4:22 AM: ------------------------------------------------------------------- My fix for EGit was merged into master: https://bugs.eclipse.org/bugs/show_bug.cgi?id=387617#c13 . I expect it to make it into EGit 2.1 which is due for Juno SR1 (http://wiki.eclipse.org/EGit/New_and_Noteworthy). It should also be available from the EGit nightly update site (according to the wiki). was (Author: adietish): my fix for EGit was merged into master: https://bugs.eclipse.org/bugs/show_bug.cgi?id=387617#c13 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12150 at 8/30/12 4:22 AM: ------------------------------------------------------------------- My fix for EGit was merged into master: https://bugs.eclipse.org/bugs/show_bug.cgi?id=387617#c13 . I expect it to make it into EGit 2.1 which is due for Juno SR1 (http://wiki.eclipse.org/EGit/New_and_Noteworthy). It should also be available from the EGit nightly update site (according to the EGit wiki). was (Author: adietish): My fix for EGit was merged into master: https://bugs.eclipse.org/bugs/show_bug.cgi?id=387617#c13 . I expect it to make it into EGit 2.1 which is due for Juno SR1 (http://wiki.eclipse.org/EGit/New_and_Noteworthy). It should also be available from the EGit nightly update site (according to the wiki). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12150: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.x) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira