HumanBrainProject / HumanBrainProject/hbp-validation-framework

Internal Server Error due to long query strings

Open
#283 1 comment 0 reactions 1 assignee View on GitHub

@apdavison is already working on this.

Since Aug 11, 2020.

REST API v2
Dominant language
Python
Stars
5
Forks
12
PR merge metrics
No merged PRs in 30d

Description

For purposes of comparing validation results, I require to fetch the results assoicated with numerous model/test instances.
So queries such as following arise:

GET https://validation-v2.brainsimulation.eu/results-extended/?model_instance_id=e7e17b98-86fd-4ede-af2b-831642ca47c9&model_instance_id=20b57bd8-7076-4f46-a361-84255b06401c&model_instance_id=233a109e-d26f-4f50-809e-1aa52d3fa84c&model_instance_id=3342e542-5fb1-45aa-b7be-69e94f809160&model_instance_id=938807e6-0d28-4d8c-9d73-95f1df1af282&model_instance_id=403d865e-417c-45fe-97cf-83a9613ae664&model_instance_id=20e69189-ab22-4967-88a0-9e719a547380&model_instance_id=a5e4a43e-444a-49c3-9435-05ab934218ca&model_instance_id=f7153820-e3db-48b8-84ca-389c50d9298a&model_instance_id=cf81d7a3-5f42-4e2e-b884-6121c6f026ba&model_instance_id=d6713000-db8b-4c33-aabf-a13a5224b404&model_instance_id=da1b7cc5-c9af-46d1-81fe-bc4661077e7d&size=1000000

(I have also tested with /results/ end-point and have the same problem)

I get the following response:

500 Internal Server Error

Somewhat shorter queries seem to work (even though with delay):
GET https://validation-v2.brainsimulation.eu/results-extended/?model_instance_id=e7e17b98-86fd-4ede-af2b-831642ca47c9&model_instance_id=20b57bd8-7076-4f46-a361-84255b06401c&model_instance_id=233a109e-d26f-4f50-809e-1aa52d3fa84c&model_instance_id=3342e542-5fb1-45aa-b7be-69e94f809160

It would be useful if this problem can be fixed, and we can avoid making multiple calls as it affects performance (more overhead) and also leads to unnecessary 'hacky' coding.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.