-
Notifications
You must be signed in to change notification settings - Fork 40
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
Changes to ontology (possibly around Rhea xrefs or riot) prevent full ontology build and block other pipeline builds #28404
Comments
I'm not sure the RHEA errors/warnings are the root cause of the issue here, but here's a quick report on the offending IDs:
From looking at the associated tickets, these three RHEAs are in the RHEA internal DB but not yet in the public file - they all related to recently created GO terms: id: GO:0141208 id: GO:0141207 id: GO:0141200 I see there's an additional problem with GO:0141207, where the second line needs deleting:
This has been replaced with RHEA:78471 and RHEA:78475
And this has been replaced with RHEA:78479 and RHEA:78507 That might mean that all four new RHEAs should be narrowMatch xref on the associated GO term, but I haven't checked: id: GO:0071164 |
I dont think this what is causing the problem; new RHEAs (not yet public) are allowed. (see https://wiki.geneontology.org/Guidelines_for_database_cross_references#Database_cross-references) |
I've fixed the "xref: RHEA:80271 {comment="skos:narrowMatch"}" issue in #28015. For GO:0071164, I've checked the new RHEAs, and they should all be added as narrowMatch xrefs to this term, so I'll do that now. |
Closing this issue, since this was fixed and we have another ticket to add QC for problems with the 'source' property: #28417 |
Between 8am and 4pm PT, on July 4th, the ontology build started to fail, bringing down or blocking multiple pipelines. Looking at the PRs in that window, I suspect the changes happened earlier, but took a couple of runs to sync into the build.
While the fatal build step seems to be:
The most suspicious part leading up to that seems to be this set of Rhea identifier errors:
I would also note the following oddity:
Ideally, this issue should only be closed when both of these criteria are met:
Tagging @pgaudet @balhoff @sjm41
The text was updated successfully, but these errors were encountered: