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

Make core handle extension failures #667

Closed
adamcik opened this Issue Jan 25, 2014 · 1 comment

Comments

2 participants
@adamcik
Member

adamcik commented Jan 25, 2014

Frontends/backends failing should never be able to crash the core. When this happens the components should be removed, and the threads cleaned up/stopped if possible. In the future this could allow for run time re-configuring of enabled extensions as well.

@adamcik

This comment has been minimized.

Member

adamcik commented Feb 16, 2014

As an aside to this I was talking about having a chaos monkey actor that fails messages with some percentage chance, forcing us to make sure we always handle backend/frontend errors.

@jodal jodal added this to the Core cleanup milestone Jun 22, 2014

@adamcik adamcik modified the milestones: v1.0.x, v2.0 - Core cleanup Apr 3, 2015

@adamcik adamcik self-assigned this Apr 3, 2015

@adamcik adamcik modified the milestones: v1.1 - Gapless playback, v1.0.x Apr 12, 2015

@adamcik adamcik closed this Apr 12, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment