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

NPE when registering acceptability of inactive/missing descriptions #31

Closed
apeteri opened this issue Dec 3, 2019 · 2 comments
Closed
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@apeteri
Copy link

apeteri commented Dec 3, 2019

In #30 (comment), @kaicode writes:

This line is causing the null pointer:
https://github.com/IHTSDO/snomed-owl-toolkit/blob/master/src/main/java/org/snomed/otf/owltoolkit/taxonomy/SnomedTaxonomy.java#L259

This indicates that there is an active language reference set entry for a description which
does not exist or is not active. [...] they may be referencing content which is active
January but no longer active in the July package you are using.

Could this be a "soft" error instead, that is reported with the UUID/effective time of the offending reference set member? It seems like in the current release, such exceptions result in dialect detection being broken for exported RDFS and SKOS labels (they still get tagged with the language code of the description, eg. "en", but not with eg. "en-us" if the US refset is the one having problems).

This can happen if users want to take a look at the OWL representation while doing an upgrade, where references to inactive components might not be fully cleaned up.

@kaicode
Copy link
Member

kaicode commented Dec 3, 2019

Hi @apeteri, thanks for spotting this and bringing it up. Yes, great idea. The exception handling when loading RF2 files needs some improvement here because as you say the thread loading a reference set file can just stop when an exception is thrown. We should probably check if the description exists and just log a warning if it doesn't?

Do you have capacity to write a pull request for this change, assuming that it's impacting something you are looking at? If not no problem, I should get to it in a few days.

Kind regards,
Kai

@kaicode kaicode added bug Something isn't working enhancement New feature or request labels Dec 3, 2019
@kaicode
Copy link
Member

kaicode commented Dec 3, 2019

Not sure if this is a bug or an enhancement. I intended the toolkit to only work with versions of modules which are already validated as being dependent on each other and consistent, but on the other hand being lenient and reporting warnings is good 😄.

@kaicode kaicode self-assigned this Dec 4, 2019
@kaicode kaicode closed this as completed in 840e0e8 Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants