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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent node from dying when DB unavailable by wrapping getMaintenanceTime #374

Conversation

shayneczyzewski
Copy link

Hey @timgit!

I was doing some testing on the latest release (thanks again for that BTW!) before bumping our version in Wasp and noticed if I killed the DB I could still get an error that took down node. It appears the issue is there was a call in Boss.metaMonitor to Boss.getMaintenanceTime that was not wrapped like some of the others and will blow up if no DB is available.

This small PR just wraps it the function that calls it. If you would like me to add any tests like the others, or make any other tweaks, I can as well. 馃憤馃徎

Thanks!
Shayne

@shayneczyzewski
Copy link
Author

Note, with this fix in place, what would normally cause node to die in a few minutes (via this test project) has been running for over 30min just fine. I will leave it running for several hours just to be sure there are no other periodic tasks that may cause issues.

@timgit timgit changed the base branch from master to meta-monitor-error-handling March 15, 2023 04:10
@timgit timgit merged commit d6d3f69 into timgit:meta-monitor-error-handling Mar 15, 2023
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.

None yet

2 participants