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

[core-service] Do not panic when TotalConns==0 #692

Merged
merged 1 commit into from
Feb 1, 2022

Conversation

BenjaminPelletier
Copy link
Member

This PR fixes #691 in the near-mid term. Long term, we will want to check our database client's behavior.

@BenjaminPelletier BenjaminPelletier added the P0 Highest priority; blocking usage or development label Feb 1, 2022
@barroco
Copy link
Contributor

barroco commented Feb 1, 2022

Looking at #691 description, I support the idea of checking our database client's behavior taking into account the work in #688 in a future iteration.

@BenjaminPelletier
Copy link
Member Author

I've attempted to capture the need for future work on this subject in #694

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Highest priority; blocking usage or development
Projects
None yet
Development

Successfully merging this pull request may close these issues.

core-service panics when database connection is still good
2 participants