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

failsafe mode #397

Open
fabricedesre opened this issue Apr 18, 2016 · 1 comment
Open

failsafe mode #397

fabricedesre opened this issue Apr 18, 2016 · 1 comment

Comments

@fabricedesre
Copy link
Collaborator

There are cases where we panic!(), like https://github.com/fxbox/taxonomy/blob/674b72d5d7b6eb53f1010a0048d4c4e9f4afcb58/src/tag_storage.rs#L53 because we don't have a good way to recover.

One solution to deal with this kind of situations can be to not panic, but instead to restart the foxbox in "failsafe" mode, in which we only do the bare minimum, safe things with some diagnostic to help fix the issue.

@Yoric
Copy link

Yoric commented Apr 18, 2016

In the Taxonomy back-end, I use a macro log_debug_assert! that causes a panic in debug builds and just logs in release builds. I think that it's an acceptable solution for many things.

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

No branches or pull requests

2 participants