Skip to content

Auto-retry failed connection#223

Open
marius851000 wants to merge 4 commits intoInputUsername:masterfrom
marius851000:auto-reconnect
Open

Auto-retry failed connection#223
marius851000 wants to merge 4 commits intoInputUsername:masterfrom
marius851000:auto-reconnect

Conversation

@marius851000
Copy link
Copy Markdown
Contributor

@marius851000 marius851000 commented Jul 26, 2025

This implement what is necessary to retry a failed connection (for reasons such as, for exemple, not being connection to internet on when rescrobbled start).

I have implemented exponentional back-off, it will retry every 15 minutes as worst.

An evolution I foresee is not retrying when we got the confirmation the token or configuration is invalid.

It moved the old "Service" into a "ServiceConnection" trait with two implementation (for ListenBrainz and Last.fm). The new "Service" overlay over them to persist information about them even in case of a failed initial connection.

I only tried with ListenBrainz. I would like someone to try with Last.fm. I’m a bit worried of how it would work with the initial last.fm connection system (before obtaining a token).

Fix #222

Coca162 added a commit to Coca162/nix-config that referenced this pull request Dec 20, 2025
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.

Recrobbled doesn’t try to reconnect to Listenbrainz after a failed connection

1 participant