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

Client does not sync playlist clearing actions to the server #609

Closed
gavtroy opened this issue May 28, 2023 · 5 comments
Closed

Client does not sync playlist clearing actions to the server #609

gavtroy opened this issue May 28, 2023 · 5 comments

Comments

@gavtroy
Copy link

gavtroy commented May 28, 2023

Following the changes for #567, the playlistNeedsRestoring() check prevents a playlist clearing action from being processed. Although the GUI does still show an empty playlist, other users will still see the previous playlist.

This also makes it impossible to delete persistent rooms.

@Et0h
Copy link
Contributor

Et0h commented May 28, 2023

Thanks for reporting this. I can confirm the issue but as I'm away from home I can't work on it right now. If anyone wants to try to fix this and make a PR then feel free.

@Et0h
Copy link
Contributor

Et0h commented Jun 2, 2023

@gavtroy Please try out my fix at https://github.com/Syncplay/syncplay/actions/runs/5158492715 and let me know if it works.

@gavtroy
Copy link
Author

gavtroy commented Jun 3, 2023

Deleting both definitions of playlistNeedsRestoring() looks like an accident. That version gets stuck in a connection loop for me. Assuming the correct change was return self._client.playlistMayNeedRestoring and ... then from my very limited testing it appears to work.

@Et0h
Copy link
Contributor

Et0h commented Jun 3, 2023

That's weird, thanks for letting me know. There was a definition for playlistNeedsRestoring in my PyCharm version, but it must not have committed properly for some reason. I've now updated GIT HEAD to add in the version which I was using to develop the fix and you can test with that.

@gavtroy
Copy link
Author

gavtroy commented Jun 3, 2023

Yes that seems to be working well. Thanks for coming with a fix.

@Et0h Et0h closed this as completed Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants