What is the canonical way of dealing with exceptions in backend extensions?
My understanding is that https://github.com/mopidy/mopidy/pull/1104 recently added a wrapper around most back-end calls that will just catch and log unhandled exceptions to prevent the core from crashing.
Apart from just logging fatal exceptions and trying to follow the skip-to-next-track-upon-error approach, is there another way of notifying the user that something has gone wrong and perhaps revert to some predictable state in Mopidy (e.q. current track paused, redirected to front-end landing page, or something along those lines)?
