Community
Participate
Working Groups
Basic review on SOLARIS generated the following error with git project Use org.eclipse.mylyn.review.frame.core Then I selected the "more items" a few times, scroll items up and down then: java.lang.ArrayIndexOutOfBoundsException: 1 at org.eclipse.jgit.treewalk.TreeWalk.getObjectId(TreeWalk.java:673) at org.eclipse.jgit.diff.DiffEntry.scan(DiffEntry.java:119) at org.eclipse.mylyn.internal.git.core.GitConnector.getChangeSet(GitConnector.java:124) at org.eclipse.mylyn.internal.git.ui.GetChangeSetDialog.updateChangeSet(GetChangeSetDialog.java:461) at org.eclipse.mylyn.internal.git.ui.GetChangeSetDialog.populateNextChangeSets(GetChangeSetDialog.java:292) at org.eclipse.mylyn.internal.git.ui.GetChangeSetDialog$1.widgetSelected(GetChangeSetDialog.java:258) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061) at org.eclipse.swt.custom.CCombo.listEvent(CCombo.java:1119) at org.eclipse.swt.custom.CCombo$1.handleEvent(CCombo.java:115)
Changed to mylyn versions, as the error is located in the versions git connector
Does this problem still occur with the latest EGit?
I believe this still happens when the number of commits in the repo is very small e.g. less than 10 (pretty much a brand new repo), the fault shall be within the Git UI connector itself.
Are you planning to address this for the 1.0 release?
(In reply to comment #4) > Are you planning to address this for the 1.0 release? I think it should be feasible to address this one before the GA, is it ok to target the fix for the end of next week?
Yes, we can then put it into RC3.
When the connector is resolviing the changeset list it uses a TreeWalk instance to load two commit trees to compare against (current vs parent), However when the first entry is reached no parents are present leaving the TreeWalk with a single Tree and the comparission fails. The fix is to load the same commit twice in the TreeWalk for this case, this will resolve all the entry files as additions as there is no base to compare. change is now uploaded to the gerrit server.
This is now integrated in the master branch
*** Bug 364622 has been marked as a duplicate of this bug. ***