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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Improve reliability against a crashed (and potentially restarting) TeraChem server #4

Open
coltonbh opened this issue Feb 21, 2021 · 0 comments
Open

[FEATURE] Improve reliability against a crashed (and potentially restarting) TeraChem server #4

coltonbh opened this issue Feb 21, 2021 · 0 comments
Assignees
@coltonbh
Labels
bug Something isn't working enhancement New feature or request

Comments

@coltonbh
Copy link
Contributor

TeraChem crashes a lot. The server mode crashes when TeraChem does. I need logic in the client that handles that:

  1. Some amount of retry time for connecting upon initial connect. Perhaps the server is being restarted by Docker
  2. Correct error handling when a compute job crashes TeraChem. This means something like if the check_job_compelete function raises a ServerError I should return an AtomicResult with success=False and any other details I can provide (none at the moment).
@coltonbh coltonbh added bug Something isn't working enhancement New feature or request labels Feb 21, 2021
@coltonbh coltonbh self-assigned this Feb 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@coltonbh coltonbh

Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@coltonbh