[YANGIDE-18] YangModelException: Does not exist Created: 02/Jun/16 Updated: 19/Oct/17 |
|
| Status: | Confirmed |
| Project: | yangide |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michael Vorburger | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6000 |
| Description |
|
I'm too frequently, during "normal" operation (dev workspace with like many yangtools and controller projects open in it) seeing this exception make the Error Log pop-up, when probably this should somehow be "handled" (ignored?) in the code: org.opendaylight.yangide.core.YangModelException: Does not exist |
| Comments |
| Comment by David M. Karr [ 02/Jun/16 ] |
|
We need to understand how this is happening. I can't tell anything about what's happening here by just looking at the code at TOS. This is basically telling us that something doesn't exist, and that's all. |
| Comment by David M. Karr [ 02/Jun/16 ] |
|
We could at least augment the message to include the name and full path of the resource that isn't found. That would help at least. |
| Comment by Michael Vorburger [ 02/Jun/16 ] |
|
> augment the message to include the name and full path of the resource that isn't found. That sounds like a great idea to me! If you would like to do this, then I promise to update this bug with new details next time I see it? |
| Comment by David M. Karr [ 02/Jun/16 ] |
|
Already starting to test the change. |
| Comment by David M. Karr [ 02/Jun/16 ] |
|
This change to add more info is merged. I noticed that when I set a breakpoint at this spot, it was hitting it for some odd resources, like for files in projects that definitely don't exist. Seems like there's some out of date cache in play here. I also noticed that for the instances when it hit this for me, it wasn't resulting in an error dialog. I imagine at least one of the paths that get here are just ignoring the exception if the resource "doesn't work". |
| Comment by Michael Vorburger [ 17/Jun/16 ] |
|
Re-opening this bug, this one currently definitely is not RESOLVED FIXED. Following the change to provide more details (above, thanks), I'm now seeing the Exception below - and noticed something interesting: This refers to an Eclipse Project which I have in my Workspace, but at that moment closed (I personally regularly close projects and then open them again). Could that be the root cause? Perhaps some code needs to be improved to handle closed Projects correctly? org.opendaylight.yangide.core.YangModelException: Does not exist: name[org.opendaylight.ovsdb.hwvtepsouthbound-aggregator] fullpath[/org.opendaylight.ovsdb.hwvtepsouthbound-aggregator] [omited call stack elements which are identical to original one above] |