Bugzilla – Full Text Bug Listing
| Summary: | NullPointerException at org.eclipse.egit.core.op.CommitOperation.prepareTrees(CommitOperation.java:245) | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Michael Vorburger <mike> |
| Component: | Core | Assignee: | Jens Baumgart <jens.baumgart> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | christian.halstrick, eclipseBugs, gareth.clay, jens.baumgart, mamiehling, mathias.kinzler, miker |
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Michael Vorburger
Can you reproduce this with a simple example? If your sceanrio is more complex: can you attach your zipped repository? I have not seen this anymore, and unfortunately can not offer any reproducible scenario; sorry. (May be just "harden" those lines with some if null? Else feel free to close as CANTREPRO.) I also encountered this issue on Eclipse 3.6.1 with egit 0.10.1 !ENTRY org.eclipse.core.jobs 4 2 2011-01-05 22:44:17.693 !MESSAGE An internal error occurred during: "Committing changes". !STACK 0 java.lang.NullPointerException at org.eclipse.egit.core.op.CommitOperation.prepareTrees(CommitOperation.java:245) at org.eclipse.egit.core.op.CommitOperation.access$7(CommitOperation.java:199) at org.eclipse.egit.core.op.CommitOperation$1.run(CommitOperation.java:166) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957) at org.eclipse.egit.core.op.CommitOperation.execute(CommitOperation.java:192) at org.eclipse.egit.ui.internal.actions.CommitActionHandler$2.run(CommitActionHandler.java:206) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) We are currently replacing the related deprecated code. After we have done that we should retry. An internal error occurred during: "Committing changes". java.lang.NullPointerException That's all the 'Problem Occurred' dialog box tells me when I try to commit. My project is a Latex project with the following structure: out (not tracked) src (tracked) png (tracked) document.tex (tracked tmp (not tracked) When I create a new project and attempt to make a commit it works just fine. I have tried deleting my git repo and allowing Eclipse to recreate it, I've tried to untrack everything and then re-track it. I've tried practically everything except recreating this project as a new one which I was hoping to avoid. I'm seeing this issue too with EGit 0.11.3. Same stack trace as Hans, just with a line number shift: java.lang.NullPointerException at org.eclipse.egit.core.op.CommitOperation.prepareTrees(CommitOperation.java:258) at org.eclipse.egit.core.op.CommitOperation.access$7(CommitOperation.java:201) at org.eclipse.egit.core.op.CommitOperation$1.run(CommitOperation.java:168) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957) at org.eclipse.egit.core.op.CommitOperation.execute(CommitOperation.java:194) at org.eclipse.egit.ui.internal.actions.CommitActionHandler$2.run(CommitActionHandler.java:208) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) My first few commits into an empty repository seemed to work, but now I've begun to throw a few new eclipse projects in there (on a new branch off), EGit seems unhappy. I've just updated to 0.12.0.201103040937 via the nightlies update site, and the problem is gone :) Keep up the great work guys! (In reply to comment #7) > I've just updated to 0.12.0.201103040937 via the nightlies update site, and the > problem is gone :) > > Keep up the great work guys! Thanks for your patience. We have now completely replaced the code, so if something like that occurs again, just reopen this or create a new bug. This bug should be kept open as it still occurs in the most-recent daily. Against an existing project, I used "Team" to create a new GIT repository (which properly showed-up), then "Added" all of the files to it, then tried to "Commit." The exception occurred repeatedly and the commit did not appear to succeed. A command-line "git commit" appeared to complete the operation. |