Thomas Adamcik
Thomas Adamcik
https://github.com/mopidy/mopidy-spotify/issues/110#issuecomment-1141550914 made me realize that we should probably strip out any auth info in URLs we log. I don't think we can ensure that plugins don't screw this up, but...
A lot of things have wound up as frontends inside mopidy that don't need to be. Especially things that use GPIO or raw memory and thus end up running as...
At least the following extension should be setting correct proxy settings if they aren't already: - [x] ~~Dirble~~ (deprecated, service no longer available) - [ ] SoundCloud - [x] Spotify...
http://goo.gl/YhjzyZ has the current proposed design for supporting this and elaborates on what this issue covers.
Would allow for things like soundcloud mathcing `http://soundcloud.com` things and handling them instead of stream, which would just be a fallback. We could also just have a generic fallback where...
We currently don't have any mechanism for letting users know when something goes wrong. This should probably be fixed.
For use in the stream backend and other things that aren't tracks but streams.
Not seen this failure mode before, not sure how to trigger it. ``` 016-01-24 20:53:39,071 ERROR [HttpFrontend-14] /home/adamcik/dev/mopidy-virtualenv/local/lib/python2.7/site-packages/pykka/actor.py:269 pykka Unhandled exception in HttpFrontend (urn:uuid:a5a96e79-06a9-4697-89b9-76561b06f2e8): Traceback (most recent call last): File...
I can consistently trigger this in the gst1 branch with spotify tracks. I've not checked if it is present in 1.1.x or without spotify yet.
At the time we handle the new segment indicating track change / seek and the stream changed event the query position we get is typically still being reported as the...