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

Reset maximum skip limit #43

Closed
jcass77 opened this issue Jan 26, 2016 · 1 comment
Closed

Reset maximum skip limit #43

jcass77 opened this issue Jan 26, 2016 · 1 comment

Comments

@jcass77
Copy link
Member

jcass77 commented Jan 26, 2016

When more than five tracks in a row are unplayable, the 'maximum skip limit' is enforced to avoid the client from exceeding Pandora's internal request thresholds.

This works as expected, but the limit is never reset again once it has been reached, and the only way to resume playback is to restart Mopidy. Log contains:

2016-01-26 06:07:28,518 - WARNING  Maximum track skip limit (5) exceeded.
2016-01-26 06:07:28,521 - WARNING  Track is not playable: pandora:track:788279271243133277:4b93698ca1d1b60a1e496911cad2e191a0645cda5c3ab18ebcc5328266209b4b2fe04a60810b426142cc58b1431e06c45e5d5323ac6195f3

A sensible point at which to reset the counter might be when the user does a manual refresh in the web client, or switches to a different station.

@jcass77
Copy link
Member Author

jcass77 commented Jan 26, 2016

The rest should now occur whenever the user browses to another folder.

rgov pushed a commit to rgov/mopidy-pandora that referenced this issue Feb 26, 2017
Increment pydora dependency to 1.7.0.
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