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
The above description is copied from a related ticket where we replaced the accession of the old GTEX with the new one. That is a temporary fix where we hardcoded that specific accession.
The gene expression view showing properly, while the box and transcripts view are taking too long time to response for E-GTEX-8.
The above description is copied from a related ticket where we replaced the accession of the old GTEX with the new one. That is a temporary fix where we hardcoded that specific accession.
The gene expression view showing properly, while the box and transcripts view are taking too long time to response for E-GTEX-8.
We have the 500 issue as shown in the screenshot I shared above, so the gene search result will disappear. It is actually a performance issue, if you try on local server url, it is working fine.
, e.g. on prod: http://wp-p1m2-98:8080/gxa/experiments/E-GTEX-8/Results?specific=true&geneQuery=%25[…]D&cutoff=%257B%2522value%2522%253A0.5%257D&unit=%2522TPM%2522.
we can do now quickly to 'fix' this is to block the box and transcript view for the new GTEX version too and then have a think on what to do next.
We need to find a way to properly fix this 500 error coming from our backend app. It is probably a timeout issue.
The text was updated successfully, but these errors were encountered: