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

player: when playback error because no connection, stop song and show loading. When connection back, resume playing #136

Conversation

mattcarter11
Copy link
Contributor

@mattcarter11 mattcarter11 commented Dec 15, 2024

What is it?

  • New feature (user facing)
  • Update to existing feature (user facing)
  • Bugfix (user facing)
  • Translations
  • Codebase improvements or refactors (dev facing)
  • Other

Description of the changes in your PR

  • add logic to handle error when no connection
  • expose flag when player is waiting for connection
  • add logic to resume playing on connection
  • add error message when this happens

Before/After Screenshots/Screen Record

  • Before: Nothing
  • After: Changing mode from the player (or settings) -> Show what mode you have changed
  • Before: Nothing
  • After: On error -> display what the player does (according to your settings)

Closes #181

Due diligence

  • I read the contribution guidelines.
  • I understand that in the event of merge conflicts, I may be asked to rebase my branch on top of the dev branch, instead of resolving them by merging dev into my own branch

@mattcarter11 mattcarter11 force-pushed the retry-on-play-fail-and-no-connection branch from 63a937d to 6595fe3 Compare December 18, 2024 23:03
@mikooomich
Copy link
Collaborator

@mattcarter11 There are some weirdness with this implementation. LMK what you think of my changes (in the last commit)

@mikooomich mikooomich force-pushed the retry-on-play-fail-and-no-connection branch 2 times, most recently from 66a0577 to ff65336 Compare January 1, 2025 18:41
@mattcarter11
Copy link
Contributor Author

mm.... when I did this it was because I thought it would be better to allow the user to choose what to do on error.
Having by default on connection error wait for reconnection I think is fine. But enabling the user to choose skip and then have it's behavior stop I find weird.

Maybe we should just remove the setting and leave the original logic with the wait on connection error logic before.

@mikooomich
Copy link
Collaborator

Alright, sounds good, lmk when you've got that sorted out. Just to confirm, wait to reconnect becomes it's own toggle on/off, and skip remains an on/off?

(Also apologies for the conflicts I caused with your prs. I could rebase for you but that mucks with authorship, I'm not sure what your preferences are)

@mattcarter11
Copy link
Contributor Author

I meant no toggles at all.

When on error, if it's connection related, wait to reconnect, if not do the old skip twice then pause.

mattcarter11 and others added 5 commits January 6, 2025 10:40
… loading. When connection back, start playing again
* Resurrect runaway diesel engine protection for auto skip
* Re-order if else such to show error message on auto skip
* Separate wait to reconnect on it's own
@mattcarter11 mattcarter11 force-pushed the retry-on-play-fail-and-no-connection branch from 598a435 to f4383fb Compare January 6, 2025 10:05
@mattcarter11
Copy link
Contributor Author

@mikooomich all done

@mikooomich
Copy link
Collaborator

@mattcarter11 sorry for bothering you again, there are some nasty conflicts with visible offline 2.0 that I'm not too sure what happened. Please take a look when convenient

@mattcarter11 mattcarter11 deleted the retry-on-play-fail-and-no-connection branch January 7, 2025 06:20
@mattcarter11
Copy link
Contributor Author

I'll open the pr once all fixed

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

Successfully merging this pull request may close these issues.

Skipping songs without touching the next button
2 participants