geneontology / go-fastapi

https://api.geneontology.org/
5 stars 3 forks source link

"Internal Server Error" from /api/taxon/{taxon}/models #94

Open kimrutherford opened 4 months ago

kimrutherford commented 4 months ago

Hi.

I'm getting an Internal Server Error from /api/taxon/{taxon}/models when looking up NCBITaxon:4896 (pombe).

I tried on the webpage and with curl:

curl -X 'GET' \
  'https://api.geneontology.org/api/taxon/NCBITaxon%3A4896/models' \
  -H 'accept: application/json'

The error is returned after 60 seconds.

sierra-moxon commented 4 months ago

I replicated this locally today; looking into it.

kimrutherford commented 3 months ago

Hi. Has there been any progress on this issue? We'd like to use this API to update PomBase with the pombe GO-CAM details.

Thanks!

kltm commented 3 months ago

@kimrutherford Unfortunately, there has not been much progress here with meetings and some other things that have come up. This is still in the queue though.

Also see https://github.com/geneontology/noctua/issues/895#issuecomment-2167022756

kimrutherford commented 3 months ago

Hi. I just tried this:

curl -X 'GET' \
  'https://api.geneontology.org/api/taxon/NCBITaxon%3A4896/models' \
  -H 'accept: application/json'

but got "Internal Server Error" after 60 seconds.

sierra-moxon commented 3 months ago

Thanks for the report @kimrutherford - I still need to deploy the fix to the API server :)

kimrutherford commented 2 months ago

Hi @sierra-moxon

I'm still getting the "Internal Server Error". We'd like to use this endpoint for getting GO-CAMs details for PomBase.

kimrutherford commented 1 month ago

Hi.

Sorry to bother you again about this. The API was working yesterday but today it's back to giving "Internal Server Error":

> time curl -X 'GET' \
  'https://api.geneontology.org/api/taxon/NCBITaxon%3A4896/models' \
  -H 'accept: application/json'

gives:

Internal Server Error
real    1:01.14
user    0.021
sys     0.007
maxmem  13 MB
faults  0

It always takes 60 seconds to fail.

Oddly, the API calls that succeeded yesterday also took 60 seconds.

sierra-moxon commented 1 month ago

@kimrutherford - no bother at all - I am hacking away at getting the fixes for these deployed. will take a look here.