| Summary: | "Failed to add resource to index" error for a subsequent "Add to Index" | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Tomasz Zarna <tomasz.zarna> |
| Component: | Core | Assignee: | Jens Baumgart <jens.baumgart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | dariusz.luksza, jens.baumgart, matthias.sohn, robin |
| Version: | 1.2 | ||
| Target Milestone: | 1.3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tomasz Zarna
Worked fine when repeated after a while. Just now I noticed that "git status" shows me a lot of changes (staged) for files I haven't touched. So far these are EOL diffs, but still it's a mess. Bumping severity. Proposed a fix for missing unlock calls in finally blocks: http://egit.eclipse.org/r/4859 But I assume this is not the root cause of the problem. Currently the AddToIndexOperation provides the input resources as scheduling rule. This is wrong because this suggests that two Add To Index Jobs could run in parallel if the resources belong to the same Git repository. A better solution would be using a scheduling rule with all projects of the related Git repository. The scheduling rules of other EGit operations need to be checked, too. merged http://egit.eclipse.org/r/4859 as 6b68574c5e3585620736b1a70ce92984c9f18cab Fix proposed: http://egit.eclipse.org/r/4871 The fix avoids two add Jobs running in parallel. (In reply to comment #5) > Fix proposed: http://egit.eclipse.org/r/4871 > > The fix avoids two add Jobs running in parallel. The fix avoids two add Jobs running in parallel if the Jobs are related to resources belonging to the same Git repository. merged http://egit.eclipse.org/r/4871 as 99354e31eee9a6e73c394fc4a6be90b32956dec2 |