Skip to content

Feature/finished/iia 2531 illegalstateexception caught to not display dialog#641

Merged
jdsmithsos merged 6 commits intoikmdev:mainfrom
jdsmithsos:feature/finished/IIA-2531-illegalstateexception-caught-to-not-display-dialog
Aug 14, 2025
Merged

Feature/finished/iia 2531 illegalstateexception caught to not display dialog#641
jdsmithsos merged 6 commits intoikmdev:mainfrom
jdsmithsos:feature/finished/IIA-2531-illegalstateexception-caught-to-not-display-dialog

Conversation

@jdsmithsos
Copy link
Contributor

Jira ticket: https://ikmdev.atlassian.net/browse/IIA-2531

Summary of changes:

  • Added try catch for IllegalStateException where this was occurring
    • FetchChildren
    • MultiParentGraphCell
    • MultiParentGraphCellSkin
    • MultiParentGraphViewController

Even with this change, there are still menu behavior issues that need to be addressed in separate tickets:

  • Multiple items are checked in the Excluded menu, which I assume is being caused by no data for the module type
  • e.g. Select Development, then select Primordial
  • Both Development and Primordial are checked
  • This occurs both before the change, and after the change

Before changes:

Select Exclude all.

image

The IllegalStateException dialog was being displayed.

image

And both "no exclusions" and "exclude all" are checked.

image

After changes:

The IllegalStateException dialog is no longer displayed.

image

And the "no exclusions" menu item is NOT checked. "exclude all" and the other module menu items are checked correctly.

image

… occurs when the view coordinate menu Stamp exclude filter is changed
disclosureVisible = methodTreeItem != null && !methodTreeItem.isLeaf();
} catch (IllegalStateException e) {
LOG.error("IllegalStateException checking leaf", e);
}
Copy link
Contributor

@carldea carldea Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, why are we getting IllegalStateExceptions?
is there a way to check state before executing .isLeaf()? Just feel we are surrounding code in places to ignore exception. I'm fine with this solution, but i'm concerned if we are hiding the real problem.

Could we ask @jperedadnr if this is a good solution for now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, lets ask if this solution makes sense. We should know why the exceptions happen. Perhaps if the exception is valid a different dialog should be displayed with user readable text rather than the exception dialog.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should go ahead and merge this fix, since the view coordinates is responsible for querying results. the result may not make sense to the TreeView. After a exclude modules filter option.

@jdsmithsos jdsmithsos marked this pull request as draft August 14, 2025 19:09
@jdsmithsos jdsmithsos marked this pull request as ready for review August 14, 2025 19:40
Copy link
Contributor

@carldea carldea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good enough for now. We'll have to find out if it even makes sense using those filter options.

@jdsmithsos jdsmithsos merged commit ccb918a into ikmdev:main Aug 14, 2025
7 checks passed
@jdsmithsos jdsmithsos deleted the feature/finished/IIA-2531-illegalstateexception-caught-to-not-display-dialog branch August 18, 2025 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants