mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1029] Snapcast subprocess quits on non-fatal error #489
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#489
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mrplumber on GitHub (Jul 30, 2022).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1029
Compiled new version 0.4.2 today with
--release --no-default-features --features alsa-backend,with-dns-sdbuild options on Linux Debian 11 amd64.Unfortunately new librespot generates error as soon as I connect to it from my Windows PC on the local network using official Spotify app and then the same error on disconnect:
[2022-07-30T14:37:18Z ERROR librespot_core::session] could not dispatch command: Service unavailable { error handling Mercury response: MercuryResponse { uri: "social-connect/v2/session_update", status_code: 200, payload: [[<sequence of numbers separated by commas>]] } }Previous version works fine.
@roderickvd commented on GitHub (Jul 30, 2022):
Are you sure this is on the released 0.4.2 and not on
dev? This seems like a message that onlydevwould emit and there it is non-fatal.Please post the full logs.
@mrplumber commented on GitHub (Jul 30, 2022):
I recloned the repo and rebuilt with them same build options, but still get the same error. Bellow is verbose output of running program:
I edited out some sensible fields.
@roderickvd commented on GitHub (Jul 30, 2022):
Indeed this is not 0.4.2 but
dev(so after 0.4.2 release). I might update the version number indevto clarify. If you want the stable 0.4.2 then please checkout the tagged release.Still what doesn't work though? It's correct that
devdoesn't handle thesocial-connectsubscription yet. That song should play fine without it, it's an error you may safely ignore.@mrplumber commented on GitHub (Jul 30, 2022):
I am using librespot as a subprocess of snapcast server. It seams that snapserver doesn't like librespot emmiting errors and it stops when this happens. Anyway I will try your suggestion. Thank you for your efforts.
@roderickvd commented on GitHub (Jul 30, 2022):
OK. I could change it into a warning, which is really what it should be anyway. Would that improve things?