| Summary: | NPE in 'staging' view when hard resetting on local branch | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Vadim Dmitriev <dmgloss> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | elatllat, jebcor, jens.baumgart, matthias.sohn, remy.suen, robin |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Vadim Dmitriev
I failed to reproduce this following your steps Can we avoid such problems at all? I assume the IndexDiff calculation was running while the reset was performed. Since git allows reading all the time such things can happen in reading threads, right? Just hit the same problem again, this time I was frequently switching between branches, creating, removing them etc. In contrast with the original problem this one preserves after eclipse restart. java.lang.NullPointerException at org.eclipse.egit.core.ContainerTreeIterator.<init>(ContainerTreeIterator.java:124) at org.eclipse.egit.core.ContainerTreeIterator.createSubtreeIterator(ContainerTreeIterator.java:132) at org.eclipse.jgit.treewalk.AbstractTreeIterator.createSubtreeIterator(AbstractTreeIterator.java:527) at org.eclipse.jgit.treewalk.TreeWalk.enterSubtree(TreeWalk.java:907) at org.eclipse.jgit.treewalk.TreeWalk.next(TreeWalk.java:566) at org.eclipse.jgit.lib.IndexDiff.diff(IndexDiff.java:284) at org.eclipse.egit.ui.internal.staging.StagingView.doReload(StagingView.java:1085) at org.eclipse.egit.ui.internal.staging.StagingView.access$24(StagingView.java:1074) at org.eclipse.egit.ui.internal.staging.StagingView$24.run(StagingView.java:1014) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Does refreshing all projects help? related(In reply to comment #4) > Does refreshing all projects help? related bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=377644 Implementation of ContainerTteeIterator has changed in the mean time. The repository is no longer queried. Does the problem also occur with the latest EGit from the nightly build? I was running into the same problem and upgrading to the latest Egit nightly build fixed it. |