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

librespot panics with subscription terminated #185

Closed
cortegedusage opened this Issue May 14, 2017 · 22 comments

Comments

Projects
None yet
5 participants
@cortegedusage

librespot panics with;
thread 'main' panicked at 'subscription terminated', /build/arm-unknown-linux-gnueabihf/release/build/librespot-376aadb7929f1a50/out/lib.rs:615
note: Run with RUST_BACKTRACE=1 for a backtrace.

it's only with my wife's account which is part of our familly account, mine and others are working fine.
any idea's?

@cortegedusage

This comment has been minimized.

Show comment
Hide comment
@cortegedusage

cortegedusage May 14, 2017

btw the account is working well in both ios app and windows app, so it is a premium account.

btw the account is working well in both ios app and windows app, so it is a premium account.

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

Thanks for bringing up this issue.
subscription terminated is likely to be talking about an internal channel's subscription, which are used within librespot to communicate between threads, nothing to do with your Spotify account subscription.

Could you run librespot with the RUST_BACKTRACE=1 environment variable, and the --verbose command line argument and post the full log please ?

Owner

plietar commented May 15, 2017

Thanks for bringing up this issue.
subscription terminated is likely to be talking about an internal channel's subscription, which are used within librespot to communicate between threads, nothing to do with your Spotify account subscription.

Could you run librespot with the RUST_BACKTRACE=1 environment variable, and the --verbose command line argument and post the full log please ?

@cortegedusage

This comment has been minimized.

Show comment
Hide comment
@cortegedusage

cortegedusage May 15, 2017

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

Yes, run librespot like this :

RUST_BACKTRACE=1 path/to/librespot --name NAME --verbose ARGS...
Owner

plietar commented May 15, 2017

Yes, run librespot like this :

RUST_BACKTRACE=1 path/to/librespot --name NAME --verbose ARGS...
@sashahilton00

This comment has been minimized.

Show comment
Hide comment
@sashahilton00

sashahilton00 May 15, 2017

Contributor
Contributor

sashahilton00 commented May 15, 2017

@mgmeedendorp

This comment has been minimized.

Show comment
Hide comment
@mgmeedendorp

mgmeedendorp May 15, 2017

I also have the same issue since last weekend.

INFO:librespot: librespot 30bdcaf (2017-04-29). Built on 2017-05-04.
WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }
INFO:librespot::session: Connecting to AP "gew1-accesspoint-a-4ll6.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "<username>" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
DEBUG:librespot::session: Session[0] strong=3 weak=2
INFO:librespot::session: Country: "NL"
DEBUG:librespot::audio_backend::pulseaudio: Using PulseAudio sink
thread 'main' panicked at 'subscription terminated', /home/osmc/librespot/target/release/build/librespot-6d6a71d2e5f5cb52/out/lib.rs:614
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:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
   6: <librespot::spirc::SpircTask as futures::future::Future>::poll
   7: librespot::main
   8: std::panicking::try::do_call
             at /checkout/src/libstd/panicking.rs:454
   9: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  10: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:57
  11: __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Dispatch
DEBUG:librespot::session: drop Session[0]
thread '<unnamed>' panicked at 'cannot access stderr during shutdown', /checkout/src/libcore/option.rs

Hope it's helpful

mgmeedendorp commented May 15, 2017

I also have the same issue since last weekend.

INFO:librespot: librespot 30bdcaf (2017-04-29). Built on 2017-05-04.
WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }
INFO:librespot::session: Connecting to AP "gew1-accesspoint-a-4ll6.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "<username>" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
DEBUG:librespot::session: Session[0] strong=3 weak=2
INFO:librespot::session: Country: "NL"
DEBUG:librespot::audio_backend::pulseaudio: Using PulseAudio sink
thread 'main' panicked at 'subscription terminated', /home/osmc/librespot/target/release/build/librespot-6d6a71d2e5f5cb52/out/lib.rs:614
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:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
   6: <librespot::spirc::SpircTask as futures::future::Future>::poll
   7: librespot::main
   8: std::panicking::try::do_call
             at /checkout/src/libstd/panicking.rs:454
   9: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  10: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:57
  11: __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Dispatch
DEBUG:librespot::session: drop Session[0]
thread '<unnamed>' panicked at 'cannot access stderr during shutdown', /checkout/src/libcore/option.rs

Hope it's helpful

@markubiak

This comment has been minimized.

Show comment
Hide comment
@markubiak

markubiak May 15, 2017

Yup. Same issue, same backtrace, same timeframe. I'm thinking Spotify had some serious backend change happen. Note that spotify-connect-web still does work for me, which is odd.

Just gonna put this out there, it's an excerpt from the libspotify page:

Please note that we have removed the LibSpotify binaries from our website in an effort to phase out the usage of this deprecated library. LibSpotify has been considered deprecated since 2015 and will be shut down in 2017, so we want to ensure that all developers’ efforts and attention are focused on newer and better APIs that we actively support and maintain. These APIs include the Web API, iOS and Android SDKs, and upcoming embedded libraries for Windows, Mac OS X and Linux. More information regarding upcoming libraries will be provided in the coming months.

Based on this information, I would assume that this means libspotify APIs (the ones reverse engineered here) have been dropped. But spotify-connect-web uses the same API and is still working? I'd be amazed if Spotify specifically went after this project, as I don't think it harms anything...

Yup. Same issue, same backtrace, same timeframe. I'm thinking Spotify had some serious backend change happen. Note that spotify-connect-web still does work for me, which is odd.

Just gonna put this out there, it's an excerpt from the libspotify page:

Please note that we have removed the LibSpotify binaries from our website in an effort to phase out the usage of this deprecated library. LibSpotify has been considered deprecated since 2015 and will be shut down in 2017, so we want to ensure that all developers’ efforts and attention are focused on newer and better APIs that we actively support and maintain. These APIs include the Web API, iOS and Android SDKs, and upcoming embedded libraries for Windows, Mac OS X and Linux. More information regarding upcoming libraries will be provided in the coming months.

Based on this information, I would assume that this means libspotify APIs (the ones reverse engineered here) have been dropped. But spotify-connect-web uses the same API and is still working? I'd be amazed if Spotify specifically went after this project, as I don't think it harms anything...

@sashahilton00

This comment has been minimized.

Show comment
Hide comment
@sashahilton00

sashahilton00 May 15, 2017

Contributor

the apis libspotify uses are no different to the once the Spotify clients use, and neither are the the ones librespot uses. Paul mentioned earlier that the subscription terminated message is a bug in librespot.

Contributor

sashahilton00 commented May 15, 2017

the apis libspotify uses are no different to the once the Spotify clients use, and neither are the the ones librespot uses. Paul mentioned earlier that the subscription terminated message is a bug in librespot.

@markubiak

This comment has been minimized.

Show comment
Hide comment
@markubiak

markubiak May 15, 2017

Alright, that's a bit reassuring at least. Rather odd that it randomly appeared for several users with previously working binaries out of essentially nowhere. My logs are pretty much identical but if there's any extra information I could provide please let me know.

Alright, that's a bit reassuring at least. Rather odd that it randomly appeared for several users with previously working binaries out of essentially nowhere. My logs are pretty much identical but if there's any extra information I could provide please let me know.

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

Thanks for the detailed reports. I can't reproduce it yet but I'm looking into it.

@markubiak What does the Connecting to AP line say at the start of the log ? I'm thinking Spotify might have made a small change to the protocol which is incompatible with my implementation, and it's rolling out to servers incrementally.

Owner

plietar commented May 15, 2017

Thanks for the detailed reports. I can't reproduce it yet but I'm looking into it.

@markubiak What does the Connecting to AP line say at the start of the log ? I'm thinking Spotify might have made a small change to the protocol which is incompatible with my implementation, and it's rolling out to servers incrementally.

@cortegedusage

This comment has been minimized.

Show comment
Hide comment
@cortegedusage

cortegedusage May 15, 2017

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

I've pushed a commit which might fix it, and one which adds more debug information to the log.
Could you please give it a try ?

Owner

plietar commented May 15, 2017

I've pushed a commit which might fix it, and one which adds more debug information to the log.
Could you please give it a try ?

@markubiak

This comment has been minimized.

Show comment
Hide comment
@markubiak

markubiak May 15, 2017

Hi Paul,

Here's my backtrace, which indicates that the server is "guc3-accesspoint-a-wmnz.ap.spotify.com". I am in the Eastern US, if that helps. Repetitive tests connected to "guc3-accesspoint-a-4nls.ap.spotify.com", "guc3-accesspoint-a-k7r9.ap.spotify.com", etc.

RUST_BACKTRACE=1 librespot -n "TESTING" -v
INFO:librespot: librespot 871e9e8 (2017-03-26). Built on 2017-04-13.
WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
DEBUG:librespot::authentication::discovery: Post "/" {}
INFO:librespot::session: Connecting to AP "guc3-accesspoint-a-wmnz.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "markubiak" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
INFO:librespot::audio_backend::alsa: Using alsa sink
DEBUG:librespot::session: Session[0] strong=3 weak=2
thread 'main' panicked at 'subscription terminated', /home/travis/build/herrernst/librespot/target/arm-unknown-linux-gnueabihf/release/build/librespot-cbf31f11fa905ab0/out/lib.rs:615
stack backtrace:
   1: 0x54f1675b - std::sys::imp::backtrace::tracing::imp::write::h6e3058ba9f483d85
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2: 0x54f1aef3 - std::panicking::default_hook::{{closure}}::h6573be427de316b7
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:351
   3: 0x54f1a987 - std::panicking::default_hook::h227ecb2b238172e9
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:367
   4: 0x54f1b3e7 - std::panicking::rust_panic_with_hook::h2b1e04abef091579
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:555
   5: 0x54c19453 - std::panicking::begin_panic::h0e79edc1246bda43
   6: 0x54c8456b - <librespot::spirc::SpircTask as futures::future::Future>::poll::haee5d868d80d480f
   7: 0x54bf5c3b - librespot::main::hdd6ca9936aaf6545
   8: 0x54f221f3 - __rust_maybe_catch_panic
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libpanic_unwind/lib.rs:98
   9: 0x54f1ba93 - std::rt::lang_start::hadd6e99f3c8b00a8
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:436
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panic.rs:361
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/rt.rs:57
  10: 0x76cf3293 - __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Session[0]
DEBUG:librespot::mercury: drop MercuryManager
DEBUG:librespot::session: drop Dispatch

My desktop and raspberry pi both experience the same issue in an identical fashion. I'll try the new commit and also try a VPN to somewhere in Europe.

Hi Paul,

Here's my backtrace, which indicates that the server is "guc3-accesspoint-a-wmnz.ap.spotify.com". I am in the Eastern US, if that helps. Repetitive tests connected to "guc3-accesspoint-a-4nls.ap.spotify.com", "guc3-accesspoint-a-k7r9.ap.spotify.com", etc.

RUST_BACKTRACE=1 librespot -n "TESTING" -v
INFO:librespot: librespot 871e9e8 (2017-03-26). Built on 2017-04-13.
WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
DEBUG:librespot::authentication::discovery: Post "/" {}
INFO:librespot::session: Connecting to AP "guc3-accesspoint-a-wmnz.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "markubiak" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
INFO:librespot::audio_backend::alsa: Using alsa sink
DEBUG:librespot::session: Session[0] strong=3 weak=2
thread 'main' panicked at 'subscription terminated', /home/travis/build/herrernst/librespot/target/arm-unknown-linux-gnueabihf/release/build/librespot-cbf31f11fa905ab0/out/lib.rs:615
stack backtrace:
   1: 0x54f1675b - std::sys::imp::backtrace::tracing::imp::write::h6e3058ba9f483d85
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2: 0x54f1aef3 - std::panicking::default_hook::{{closure}}::h6573be427de316b7
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:351
   3: 0x54f1a987 - std::panicking::default_hook::h227ecb2b238172e9
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:367
   4: 0x54f1b3e7 - std::panicking::rust_panic_with_hook::h2b1e04abef091579
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:555
   5: 0x54c19453 - std::panicking::begin_panic::h0e79edc1246bda43
   6: 0x54c8456b - <librespot::spirc::SpircTask as futures::future::Future>::poll::haee5d868d80d480f
   7: 0x54bf5c3b - librespot::main::hdd6ca9936aaf6545
   8: 0x54f221f3 - __rust_maybe_catch_panic
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libpanic_unwind/lib.rs:98
   9: 0x54f1ba93 - std::rt::lang_start::hadd6e99f3c8b00a8
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panicking.rs:436
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/panic.rs:361
                at /buildslave/rust-buildbot/slave/stable-dist-rustc-cross-host-linux/build/src/libstd/rt.rs:57
  10: 0x76cf3293 - __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Session[0]
DEBUG:librespot::mercury: drop MercuryManager
DEBUG:librespot::session: drop Dispatch

My desktop and raspberry pi both experience the same issue in an identical fashion. I'll try the new commit and also try a VPN to somewhere in Europe.

@mgmeedendorp

This comment has been minimized.

Show comment
Hide comment
@mgmeedendorp

mgmeedendorp May 15, 2017

It seems like I'm getting the same error with the latest update. I'm in the Netherlands if that is relevant.

INFO:librespot: librespot 7c237c7 (2017-05-15). Built on 2017-05-15.
WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }
INFO:librespot::session: Connecting to AP "gew1-accesspoint-a-0cpb.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "<username>" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
DEBUG:librespot::audio_backend::pulseaudio: Using PulseAudio sink
DEBUG:librespot::session: Session[0] strong=3 weak=2
INFO:librespot::session: Country: "NL"
thread 'main' panicked at 'subscription terminated', /home/osmc/librespot/target/release/build/librespot-6d6a71d2e5f5cb52/out/lib.rs:614
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:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
   6: <librespot::spirc::SpircTask as futures::future::Future>::poll
   7: librespot::main
   8: std::panicking::try::do_call
             at /checkout/src/libstd/panicking.rs:454
   9: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  10: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:57
  11: __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Session[0]
DEBUG:librespot::mercury: drop MercuryManager
DEBUG:librespot::session: drop Dispatch

It seems like I'm getting the same error with the latest update. I'm in the Netherlands if that is relevant.

INFO:librespot: librespot 7c237c7 (2017-05-15). Built on 2017-05-15.
WARN:mdns: Failed to register IPv6 receiver: Error { repr: Os { code: 19, message: "No such device" } }
INFO:librespot::session: Connecting to AP "gew1-accesspoint-a-0cpb.ap.spotify.com:4070"
INFO:librespot::session: Authenticated as "<username>" !
DEBUG:librespot::session: new Session[0]
DEBUG:librespot::spirc: new Spirc[0]
DEBUG:librespot::mercury: new MercuryManager
DEBUG:librespot::player: new Player[0]
DEBUG:librespot::audio_backend::pulseaudio: Using PulseAudio sink
DEBUG:librespot::session: Session[0] strong=3 weak=2
INFO:librespot::session: Country: "NL"
thread 'main' panicked at 'subscription terminated', /home/osmc/librespot/target/release/build/librespot-6d6a71d2e5f5cb52/out/lib.rs:614
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:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
   6: <librespot::spirc::SpircTask as futures::future::Future>::poll
   7: librespot::main
   8: std::panicking::try::do_call
             at /checkout/src/libstd/panicking.rs:454
   9: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  10: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:57
  11: __libc_start_main
DEBUG:librespot::spirc: drop Spirc[0]
DEBUG:librespot::player: drop Player[0]
DEBUG:librespot::session: drop Session[0]
DEBUG:librespot::mercury: drop MercuryManager
DEBUG:librespot::session: drop Dispatch
@cortegedusage

This comment has been minimized.

Show comment
Hide comment
@cortegedusage

cortegedusage May 15, 2017

@markubiak

This comment has been minimized.

Show comment
Hide comment
@markubiak

markubiak May 15, 2017

I'm also getting that it's not location dependent, VPN has no effect. Most recent commit sees no change from previous behavior.

I'm also getting that it's not location dependent, VPN has no effect. Most recent commit sees no change from previous behavior.

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

@cortegedusage I might take you up on your offer of using your account. If you want to change your password and send me your credentials to lietarp@gmail.com that would be awesome.

Owner

plietar commented May 15, 2017

@cortegedusage I might take you up on your offer of using your account. If you want to change your password and send me your credentials to lietarp@gmail.com that would be awesome.

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

I can now reproduce this thanks to @cortegedusage, looking into it

Owner

plietar commented May 15, 2017

I can now reproduce this thanks to @cortegedusage, looking into it

@plietar plietar closed this in 6f24e3b May 15, 2017

@plietar

This comment has been minimized.

Show comment
Hide comment
@plietar

plietar May 15, 2017

Owner

Should be fixed now.
Thanks @cortegedusage @angerrit @Seremis @markubiak. Please let me know if you're still having issues.

Owner

plietar commented May 15, 2017

Should be fixed now.
Thanks @cortegedusage @angerrit @Seremis @markubiak. Please let me know if you're still having issues.

@markubiak

This comment has been minimized.

Show comment
Hide comment
@markubiak

markubiak May 16, 2017

Thanks for the incredibly fast fix! Everything is working great for me now.

Thanks for the incredibly fast fix! Everything is working great for me now.

@cortegedusage

This comment has been minimized.

Show comment
Hide comment
@cortegedusage

cortegedusage May 16, 2017

@mgmeedendorp

This comment has been minimized.

Show comment
Hide comment
@mgmeedendorp

mgmeedendorp May 16, 2017

Thanks for the quick fix! Everything is working perfectly now

Thanks for the quick fix! Everything is working perfectly now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment