search

RobokopU24 / Feedback

Feedback on the ROBOKOP project
https://robokop.renci.org
0 stars 0 forks source link

YOBOKOP UI returning bad response for certain yeast nodes #217

Open Woozl opened 4 months ago

Woozl commented 4 months ago

We're encountering an issue with yobokop.apps.renci.org/question-builder when querying for E1BSW0_CHICK AHA1, activator of heat shock 90kDa 2 (yeast) (trembl) related to Named Thing.

query ``` { "message": { "query_graph": { "nodes": { "n0": { "name": "E1BSW0_CHICK AHA1, activator of heat shock 90kDa 2 (yeast) (trembl)", "categories": [ "biolink:Protein", "biolink:GeneProductMixin", "biolink:Polypeptide", "biolink:ChemicalEntityOrGeneOrGeneProduct", "biolink:ChemicalEntityOrProteinOrPolypeptide", "biolink:BiologicalEntity", "biolink:ThingWithTaxon", "biolink:NamedThing", "biolink:Entity", "biolink:GeneOrGeneProduct", "biolink:MacromolecularMachineMixin" ], "ids": [ "UniProtKB:E1BSW0" ] }, "n1": { "categories": [ "biolink:NamedThing" ], "name": "Named Thing" } }, "edges": { "e0": { "subject": "n0", "object": "n1", "predicates": [ "biolink:related_to" ] } } } } } ```

For just this query, the UI endpoint (POST https://yobokop.apps.renci.org/question-builder/api/quick_answer/?ara=robokop) returns 

<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->

and never hits the backend. This seems like a deployment/ingress issue, but most other queries work fine. We're wondering if something about it is triggering a firewall rule or similar issue.

hina-shah commented 5 days ago

image David looked at this, and predicts there might be an issue with qgraph or firewall/qgraph configuration. It only happens with that particular query, and happens from Robokop UI as well.