Latest obo file throws an error during parsing about go-ontology

[pgaudet]

Thanks for reporting this. Hopefully this is now fixed.

[cmpich]

I am still seeing the same issue. Downloading from the following purl:
http://purl.obolibrary.org/obo/go/snapshot/go.obo

[balhoff]

We haven't had a new snapshot release yet. They have been slow lately; we're hoping to be able to increase the frequency soon.

[cmpich]

The latest file now creates this error:
[java] charnum: -1 [java] line: subset: do_not_annotate [java] at org.obo.dataadapter.DefaultOBOParser.readSubset(DefaultOBOParser.java:889) [java] at org.obo.dataadapter.OBOParseEngine.parseTagValue(OBOParseEngine.java:647) [java] at org.obo.dataadapter.OBOParseEngine.parseTag(OBOParseEngine.java:996) [java] at org.obo.dataadapter.OBOParseEngine.doParse(OBOParseEngine.java:406) [java] at org.obo.dataadapter.AbstractParseEngine.parse(AbstractParseEngine.java:48) [java] at org.obo.dataadapter.AbstractParseEngine.parse(AbstractParseEngine.java:72) [java] at org.zfin.ontology.datatransfer.service.LoadOntology.createOboSession(LoadOntology.java:1112) [java] at org.zfin.ontology.datatransfer.service.LoadOntology.initialize(LoadOntology.java:333) [java] at org.zfin.ontology.datatransfer.service.LoadOntology.initialize(LoadOntology.java:321) [java] at org.zfin.ontology.datatransfer.service.LoadOntology.main(LoadOntology.java:175) [java] ERROR - Error while parsing Obo file [java] org.obo.dataadapter.OBOParseException: Undefined category do_not_annotate.

[balhoff]

Thanks @cmpich. This one is fixed in #27499. I'm working on adding a check to catch this.

[cmpich]

When Will I be able to see this fix?

[balhoff]

Snapshot production has been a bit sporadic recently due to some pipeline issues, but I know that @kltm is working to get one out now. Hopefully very soon.

[balhoff]

@cmpich a new snapshot is available.

[balhoff]

@cmpich FYI due to a release timing mishap, one of these problems snuck into the last official release. I created a CI check, but it went in after the release. I think we will create another release ASAP. Not sure if that will impact you, but sorry about these issues!