You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Raisin this issue because it might be an unintended error. As I work on a migration tool for nodegroups, I end up producing partially-repaired nodegroups that are likely incorrect, but in ways I do not quite know.
So far, I have been able to load them in SemTK to get useful error messages about mentions of classes / properties that don't exist in the ontology.
But with one of my recent changes, I am now seeing this exception:
http://localhost:12058/nodeGroupExecution/ingestFromCsvStringsById: Rest service call did not succeed
Details:
b'"message":"operations failed."
"rationale":"ingestion/fromCsv* threw java.lang.NullPointerException null
com.ge.research.semtk.belmont.NodeGroup.addJsonEncodedNodeGroup(NodeGroup.java:689)
com.ge.research.semtk.belmont.NodeGroup.getInstanceFromJson(NodeGroup.java:137)
com.ge.research.semtk.load.utility.SparqlGraphJson.getNodeGroup(SparqlGraphJson.java:294)
It seems a bit more catastrophic than the previous error messages I got, so it might be a candidate for a catch with some more explicit error message.
In the short term, neither colName nor URILookup (see the end of your file) should ever by null. URILookup should be [].
I can patch these things as they come up.
But properly verifying the JSON to support editing mistakes will be a non-trivial task. It would be nice to at least give a generic "JSON is bad" message.
Raisin this issue because it might be an unintended error. As I work on a migration tool for nodegroups, I end up producing partially-repaired nodegroups that are likely incorrect, but in ways I do not quite know.
So far, I have been able to load them in SemTK to get useful error messages about mentions of classes / properties that don't exist in the ontology.
But with one of my recent changes, I am now seeing this exception:
It seems a bit more catastrophic than the previous error messages I got, so it might be a candidate for a
catch
with some more explicit error message.If more details would be useful:
Click for details
The text was updated successfully, but these errors were encountered: