Skip to content

Conversation

shashankbrgowda
Copy link
Contributor

Details

NCBI api requests were failing because of connection timeout and application was going down because errors were not handled. This PR adds timeouts and returns appropriate response in case of http errors

<span class="search-param-value">{{ response.stable_id }}</span>
</div>
{% if response.code == 404 and response.message %}
{% if (response.code == 404 or response.code == 500) and response.message %}
Copy link

@azangru azangru Sep 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The id_content.html isn't really well-suited for showing the 500 error. For that matter, it doesn't really fit the 404 error either. The Venn diagram doesn't make sense here. There isn't a 'redirect' happening.

Image Image

Also, I realise that the 404 page says:

You will be redirected to the new Ensembl website, where you will find the latest genomic information

which isn't correct (the 404 page isn't redirecting user anywhere).

I don't have any concrete solutions for this; just pointing this out. I wouldn't say that this is a blocker.

@shashankbrgowda shashankbrgowda merged commit 3039370 into main Sep 17, 2025
1 check passed
@shashankbrgowda shashankbrgowda deleted the ncbi-timeout-fix branch September 22, 2025 12:10
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 this pull request may close these issues.

3 participants