Skip to content

deamon: slice bounds out of range #1043

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

Closed
tstorch opened this issue Apr 8, 2015 · 8 comments
Closed

deamon: slice bounds out of range #1043

tstorch opened this issue Apr 8, 2015 · 8 comments
Labels
kind/bug A bug in existing code (including security flaws) panic

Comments

@tstorch
Copy link

tstorch commented Apr 8, 2015

On Linux I tried to terminate the daemon with Ctrl-C. This ist what I got.

Since I have not clue about this project I can't give any further initial information. Just Thought I would leave this here.

@whyrusleeping
Copy link
Member

thats strange, this is the second time ive seen this in less than a day. must have been introduced recently. Thanks for reporting!

@whyrusleeping whyrusleeping added the kind/bug A bug in existing code (including security flaws) label Apr 8, 2015
@torarnv
Copy link
Contributor

torarnv commented Apr 8, 2015

I've been seeing this on and off while working on the shutdown stuff as well (before my changes 😄)

@jbenet
Copy link
Member

jbenet commented Apr 8, 2015

Did you have it mounted? 


Sent from Mailbox

On Wed, Apr 8, 2015 at 9:02 AM, Tristan Storch [email protected]
wrote:

On Linux I tried to terminate the daemon with Ctrl-C. This ist what I got.

Since I have not clue about this project I can't give any further initial information. Just Thought I would leave this here.

Reply to this email directly or view it on GitHub:
#1043

@tstorch
Copy link
Author

tstorch commented Apr 8, 2015

Can't say it for sure, but I'm pretty sure it was.

@jbenet
Copy link
Member

jbenet commented Apr 9, 2015

wonder if leveldb is closing before the query finishes

@whyrusleeping
Copy link
Member

@jbenet that would be my guess... any way to tell? like, leveldb.IsClosed()?

It would be super cool if it didnt panic and just returned an ErrClosed instead

@whyrusleeping
Copy link
Member

just encountered this myself.

@whyrusleeping
Copy link
Member

pretty sure this has been fixed, reopen as needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) panic
Projects
None yet
Development

No branches or pull requests

4 participants