[GH-ISSUE #228] Panic on startup: EofWhileParsingValue #152

Closed
opened 2026-02-27 19:29:07 +03:00 by kerem · 1 comment
Owner

Originally created by @tomtaylor on GitHub (May 26, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/228

I'm getting the following panic on startup, repeatedly in a loop every couple of seconds. It used to work absolutely fine, so I'm confident the credentials, etc., haven't changed.

INFO:librespot: librespot  (). Built on 2018-04-08. Build ID: t0ouC3o4
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorImpl { code: EofWhileParsingValue, line: 1, column: 0 }', /checkout/src/libcore/result.rs:906:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:68
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:57
             at /checkout/src/libstd/panicking.rs:381
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:397
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:577
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:538
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:522
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:498
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:71
   9: core::result::unwrap_failed
  10: librespot_core::cache::Cache::credentials
  11: librespot::setup
  12: librespot::main
  13: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:101
  14: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:459
             at /checkout/src/libstd/panic.rs:365
             at /checkout/src/libstd/rt.rs:58
  15: __libc_start_main
  16: _start
Originally created by @tomtaylor on GitHub (May 26, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/228 I'm getting the following panic on startup, repeatedly in a loop every couple of seconds. It used to work absolutely fine, so I'm confident the credentials, etc., haven't changed. ``` INFO:librespot: librespot (). Built on 2018-04-08. Build ID: t0ouC3o4 thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorImpl { code: EofWhileParsingValue, line: 1, column: 0 }', /checkout/src/libcore/result.rs:906:4 stack backtrace: 0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 1: std::sys_common::backtrace::_print at /checkout/src/libstd/sys_common/backtrace.rs:68 2: std::panicking::default_hook::{{closure}} at /checkout/src/libstd/sys_common/backtrace.rs:57 at /checkout/src/libstd/panicking.rs:381 3: std::panicking::default_hook at /checkout/src/libstd/panicking.rs:397 4: std::panicking::rust_panic_with_hook at /checkout/src/libstd/panicking.rs:577 5: std::panicking::begin_panic at /checkout/src/libstd/panicking.rs:538 6: std::panicking::begin_panic_fmt at /checkout/src/libstd/panicking.rs:522 7: rust_begin_unwind at /checkout/src/libstd/panicking.rs:498 8: core::panicking::panic_fmt at /checkout/src/libcore/panicking.rs:71 9: core::result::unwrap_failed 10: librespot_core::cache::Cache::credentials 11: librespot::setup 12: librespot::main 13: __rust_maybe_catch_panic at /checkout/src/libpanic_unwind/lib.rs:101 14: std::rt::lang_start at /checkout/src/libstd/panicking.rs:459 at /checkout/src/libstd/panic.rs:365 at /checkout/src/libstd/rt.rs:58 15: __libc_start_main 16: _start ```
kerem closed this issue 2026-02-27 19:29:07 +03:00
Author
Owner

@tomtaylor commented on GitHub (May 27, 2018):

It looks like a cached file was broken. I deleted the entire docker container that was running it, and recreated it. Works fine now.

<!-- gh-comment-id:392328310 --> @tomtaylor commented on GitHub (May 27, 2018): It looks like a cached file was broken. I deleted the entire docker container that was running it, and recreated it. Works fine now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#152
No description provided.