| Summary: | Trying to delete a branch caused CCE | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | daniel_megert, john.arthorne, Michael_Rennie, ob1.eclipse |
| Version: | 4.2 | Flags: | ob1.eclipse:
review+
john.arthorne: review+ |
| Target Milestone: | 4.2 RC2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Paul Webster
Similar problems in the past Bug 344704 Bug 344698 PW I wonder if this is related to the fix for bug 371130. I can reproduce this by deleting a local branch in the Git Repo view and then switching to Debug and using DEL to delete a breakpoint or switching to the Package Explorer and using DEL to delete a file. PW You could get in a state where the property tester was not valid for the selection being evaluated, and that prevented evaluation of the rest of the Expression by throwing a CoreException. http://git.eclipse.org/c/egit/egit.git/tree/org.eclipse.egit.ui/plugin.xml#n1196 See bug 352938 In 3.x we simply set the active state to false, that's what we should do here. PW Oleg, could I get you to review this: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=pwebster/bug379977 John, could you please review this as well? PW +1, makes sense from the code view point. My only suggestion is to ensure active=false for all other failure cases as well. We don't want a failing/crashing property tester resulting in a rogue handler that is always active:
try {
//err on the side of being inactive if anything goes wrong
active = false;
active = activeWhen.evaluate(context) != EvaluationResult.FALSE;
... etc ...
Released as http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=523f6369432e1fc810a86aa9c8ae2c1d9da44323 PW In I20120524-2100 PW . |