Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure threads are handled correctly for the REST API #3743

Closed
CasperWA opened this issue Feb 4, 2020 · 4 comments · Fixed by #3974
Closed

Make sure threads are handled correctly for the REST API #3743

CasperWA opened this issue Feb 4, 2020 · 4 comments · Fixed by #3974

Comments

@CasperWA
Copy link
Contributor

CasperWA commented Feb 4, 2020

No description provided.

@giovannipizzi
Copy link
Member

I imagine this is related to #3708, and means applying the changes for the REST API?
I can confirm that I am using the REST API on a Django profile, using the materials cloud feature "browse your own explore section". After a few clicks, I get 500 errors and if I go directly to the REST API, I get

{"message":"QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r)"}

(AiiDA develop branch commit 617b2df)

@CasperWA is this something that can be investigated, maybe with the help of @asle85 ?
We wanted to use the REST API for the tutorial on Wannier90+AiiDA on March 25th, but if there is this problem I fear this is not usable...

@ltalirz
Copy link
Member

ltalirz commented Apr 26, 2020

Just ran into this issue myself as well...

@CasperWA
Copy link
Contributor Author

Just ran into this issue myself as well...

"Good" to hear... I'm still creating a test to reproduce it locally and eventually make sure my fix works as intended.

@ltalirz
Copy link
Member

ltalirz commented May 11, 2020

hooray!
thanks @CasperWA and @sphuber !

@sphuber sphuber added this to the v1.2.2 milestone May 20, 2020
@sphuber sphuber modified the milestones: v1.2.2, v1.3.0 Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants