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

bad GO data hides GO data display #2595

Closed
nathandunn opened this issue Mar 21, 2021 · 2 comments · Fixed by #2596
Closed

bad GO data hides GO data display #2595

nathandunn opened this issue Mar 21, 2021 · 2 comments · Fixed by #2596

Comments

@nathandunn
Copy link
Contributor

nathandunn commented Mar 21, 2021

Using a simple curl (or from the interface), the input seems to stop saving at some point without a clear fail reason:

curl -i 'http://localhost:8080/apollo/goAnnotation/save' --header "Content-type: application/json" --request POST --data '{"aspect":"BP", "feature":"1adc7748-a921-4711-9099-40c84dc16bce", "goTerm":"GO:0046161", "goTermLabel":"heme a catabolic process (GO:0046161) ", "geneRelationship":"RO:0002331", "evidenceCode":"ECO:0000270", "evidenceCodeLabel":"IEP (ECO:0000270): inferred from expression pattern", "negate":false, "reference":"asdf:1231", "withOrFrom":["asdf:1231"], "notes":["asdfasf"],"username":"demo@demo.com","password":"demo"}'
@nathandunn
Copy link
Contributor Author

nathandunn commented Mar 21, 2021

All of the GO annotations are there, but if there are too many, they are not being rendered for some reason:

image

@nathandunn
Copy link
Contributor Author

The issue is I think bad data causing JavaScript errors:

image

nathandunn added a commit that referenced this issue Mar 21, 2021
@nathandunn nathandunn changed the title go annotation not saving sometimes bad GO data hides GO data display Mar 21, 2021
nathandunn added a commit that referenced this issue Mar 21, 2021
* fixes #2595

* updated changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant