Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cause Exception When Wrapping OperationCanceledException Into InterruptedException #25

Open
4 of 19 tasks
HeikoKlare opened this issue Nov 9, 2023 · 3 comments
Open
4 of 19 tasks
Assignees
Labels
Enhancement A Request for an Enhancement of an Existing Feature Good First Issue A Good Issue to Start Eclipse Development Platform UI Issue for Platform UI Platform Issue for Core Platform

Comments

@HeikoKlare
Copy link
Contributor

HeikoKlare commented Nov 9, 2023

Current Behavior

At several places in the Eclipse Platform and JDT code, an OperationCanceledException is transformed into an InterruptedException. In many cases, the original exception is not added as the causing exception and in several cases not even the original message is passed to the new exception, e.g. here:

                } catch (OperationCanceledException e) {
                        throw new InterruptedException();
                } catch (CoreException e) {

Expected Behavior

Every InterruptedException thrown for an OperationCanceledException should use the original message and have the original exception as its cause.

  • org.eclipse.core.tools.search.FindUnusedMembers
  • org.eclipse.search2.internal.ui.InternalSearchUI
  • org.eclipse.jface.operation.ModalContext (only wrong documentation)
  • org.eclipse.ui.operations.OperationHistoryActionHandler
  • org.eclipse.jdt.internal.core.builder.BuildNotifier
  • org.eclipse.jdt.internal.corext.refactoring.rename.RenameTypeProcessor
  • org.eclipse.jdt.internal.junit.ui.JUnitQuickFixProcessor
  • org.eclipse.jdt.internal.junit.wizards.NewTestCaseCreationWizard
  • org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter
  • org.eclipse.jdt.internal.ui.dialogs.PackageSelectionDialog
  • org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle
  • org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext
  • org.eclipse.jdt.internal.ui.wizards.buildpaths.ClasspathFixSelectionDialog
  • org.eclipse.jdt.internal.ui.wizards.buildpaths.VariableBlock
  • org.eclipse.jdt.ui.wizards.JavaCapabilityConfigurationPage
  • org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPage
  • org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPageTwo
  • org.eclipse.jdt.internal.ui.refactoring.reorg.RenameTypeWizardInputPage
  • org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper
@HeikoKlare HeikoKlare added Platform Issue for Core Platform Platform UI Issue for Platform UI Enhancement A Request for an Enhancement of an Existing Feature labels Nov 9, 2023
@fedejeanne
Copy link

@fedejeanne fedejeanne added the Good First Issue A Good Issue to Start Eclipse Development label Dec 1, 2023
@amartya4256 amartya4256 self-assigned this Dec 1, 2023
@HeikoKlare
Copy link
Contributor Author

What's the state of this? It is markes as "In Review" but no PR seems to be open on this. JDT findings have not been checked/resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A Request for an Enhancement of an Existing Feature Good First Issue A Good Issue to Start Eclipse Development Platform UI Issue for Platform UI Platform Issue for Core Platform
Projects
Status: Done
Development

No branches or pull requests

3 participants