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

Crash avoidance #13

Open
lukebarnard1 opened this issue Jul 12, 2020 · 0 comments
Open

Crash avoidance #13

lukebarnard1 opened this issue Jul 12, 2020 · 0 comments

Comments

@lukebarnard1
Copy link
Owner

Nothing should ever crash the entire nomad process otherwise all current state is lost.

Recovering a crashed session would be impossible because child processes die when the parent crashes.

I think the only option is to catch any error within a subterminal and try to revert to the previously known state, or continue in the current state. The user should probably not be told about these, but they can be logged at least.

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

1 participant