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

Fix possible cause for spurious 500s #567

Merged
merged 2 commits into from
May 17, 2017
Merged

Fix possible cause for spurious 500s #567

merged 2 commits into from
May 17, 2017

Conversation

smira
Copy link
Contributor

@smira smira commented May 15, 2017

When DB fails to be open, aptly was skipping "close" phase, so that next
request considered database to be still open (while it's closed) leading
to panic.

Fixes #431

When DB fails to be open, aptly was skipping "close" phase, so that next
request considered database to be still open (while it's closed) leading
to panic.

Fixes: #431
@smira smira added the 1.1.0 label May 15, 2017
@smira smira merged commit c9bd7b4 into master May 17, 2017
@smira smira deleted the 431-500-api branch May 17, 2017 12:33
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.

API returns HTTP status 500 after a few days
1 participant