-
Notifications
You must be signed in to change notification settings - Fork 694
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
Seeking to a non-integer position hangs clients #1756
Comments
From the Mopidy log when reproducing this:
Translated to English, Mopidy probably correctly validates that the received value should be an unsigned int, but isn't. The bug is that it from the client's perspective, Mopidy doesn't handle the problem the same way as the MPD server does. Next steps here would be to reproduce with MPD and note down details like:
Then, update Mopidy's test suite accordingly and update the implementation at https://github.com/mopidy/mopidy/blob/develop/mopidy/mpd/protocol/playback.py#L366-L382 to match MPD's behavior. |
First finding: I can confirm MPD actually seeks to the position 10.1 |
Description: as indicated by the title
Expected behaviour: Seeking to a non-integer position should have the same behavior as seeking to integer seconds.
Steps to reproduce: Using python-mpd2, while playing any song using mopidy:
The above code exits cleanly when using mpd but hangs when using mopidy.
The text was updated successfully, but these errors were encountered: