mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #413] Error in src/libcore/result.rs:1165:5 #266
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#266
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 @murphy85 on GitHub (Dec 18, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/413
I have build a Docker image, but the startup after rebuild is failing for some days now. The image loads the master branch and compiles the files. I guess there are some breaking changes in latest commit?!
[2019-12-18T16:20:15Z INFO librespot] librespot UNKNOWN (UNKNOWN). Built on 2019-12-18. Build ID: VimBUOCD
thread 'main' panicked at 'called
Result::unwrap()on anErrvalue: ParseIntError { kind: InvalidDigit }', src/libcore/result.rs:1165:5stack backtrace:
0: 0x5465dd08 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd388416be068aba
1: 0x54677ccc - core::fmt::write::hb8a0f8de322e23aa
2: 0x5465ba68 - std::io::Write::write_fmt::hc86616c02fa2c37b
3: 0x54647dbc - std::panicking::default_hook::{{closure}}::h5352f19540010e0b
4: 0x54647a44 - std::panicking::default_hook::h4d4a552a2f757720
5: 0x546484b0 - std::panicking::rust_panic_with_hook::hc8912f099044b27b
6: 0x546480b0 - std::panicking::continue_panic_fmt::hfa73573fa425363c
7: 0x54647fa8 - rust_begin_unwind
8: 0x54673b70 - core::panicking::panic_fmt::hf7ca96f7c38266d6
9: 0x54676f4c - core::result::unwrap_failed::hfe4e93cbd3983e61
10: 0x54178428 - librespot::main::h9a2ebd2f561fa29e
11: 0x54179554 - std::rt::lang_start::{{closure}}::h25f588374e523cfb
12: 0x54647f2c - std::panicking::try::do_call::h17c83e4cc139bf43
13: 0x5465fdb0 - __rust_maybe_catch_panic
14: 0x5464e6f4 - std::rt::lang_start_internal::hbef9a63b8883f1c9
15: 0x54178cc8 - main
@HEnquist commented on GitHub (Dec 23, 2019):
The master branch hasn't changed in the last ~2 months and the latest commits have mostly been minor things. All new stuff now goes to the "dev" branch first. When was your last successful build? Have you tried checking out an older version, or the "dev" branch? Does it work if you build without docker?
@ashthespy commented on GitHub (Dec 30, 2019):
Looks like you have passed in a non digit
--initial-volume@HEnquist commented on GitHub (Dec 30, 2019):
That's probably it. The example in the readme (https://github.com/murphy85/docker-librespot-alsa/blob/master/README.md) doesn't set the volume environment variable, so
--initial-volume "$SPOTIFY_INITIAL_VOLUME"will just become--initial-volume "".@ashthespy commented on GitHub (Dec 30, 2019):
According to the Dockerfile,
SPOTIFY_INITIAL_VOLUMEis set to 75.@murphy85 FWIW, I managed to build your image and get it to run, but given I am on Windos couldn't test actual playback.
PS: You seem to be loading quite a few non required packages for the alsa backend(
portaudio-dev,protobuf-dev)PSS: You probably need to load
alsa-libbefore you buildlibrespot, my first build failed because of this methinks.@HEnquist commented on GitHub (Dec 30, 2019):
Oh you're right, it is set. I read too quickly and didn't see that, sorry.
@murphy85 commented on GitHub (Dec 31, 2019):
Thank you for your comments! I'm on vacation and will check for maybe missing library and the initial volume after 13th of January. But I'm pretty sure that the cargo build loads all necessary dependencies on build, like alsa-lib if the feature is set.
@murphy85 commented on GitHub (Jan 13, 2020):
I'm sorry, it was my fault. I accidentally mixed up the order of commands in Dockerfile locally