-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
runtime error: invalid memory address or nil pointer dereference handler.go:93 #6860
Closed
Labels
kind/bug
A bug in existing code (including security flaws)
Comments
RubenKelevra
added
the
kind/bug
A bug in existing code (including security flaws)
label
Jan 31, 2020
Stebalien
added a commit
to ipfs/go-unixfs
that referenced
this issue
Feb 7, 2020
If we try deleting a bunch of files _before_ reading them, we'll panic because they haven't been loaded. This works around that by using the _link_ directly when the child hasn't been loaded. fixes ipfs/kubo#6860
Fix in ipfs/go-unixfs#81. |
Wow, that was fast! Thanks for the work! :) |
I'll let dependabot bubble it. |
This was referenced Feb 7, 2020
Merged
Jorropo
pushed a commit
to Jorropo/go-libipfs
that referenced
this issue
Jan 25, 2023
If we try deleting a bunch of files _before_ reading them, we'll panic because they haven't been loaded. This works around that by using the _link_ directly when the child hasn't been loaded. fixes ipfs/kubo#6860 This commit was moved from ipfs/go-unixfs@af8709d
Jorropo
pushed a commit
to ipfs/go-libipfs-rapide
that referenced
this issue
Mar 23, 2023
If we try deleting a bunch of files _before_ reading them, we'll panic because they haven't been loaded. This works around that by using the _link_ directly when the child hasn't been loaded. fixes ipfs/kubo#6860 This commit was moved from ipfs/go-unixfs@af8709d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version information:
go-ipfs version: 0.4.23-6ce9a355f
Repo version: 7
System version: amd64/linux
Golang version: go1.13.7
running cluster 0.12.1
Description:
Launching ipfs after update to 0.4.23, I get this panic basically every few seconds while running all kinds of cluster/ipfs commands. It stopped after a while.
The integrity of the files should be good, had no crashes or reboots since I've installed ipfs (originally 0.4.22) and the files are stored on a ZFS filesystem which shows no consistency errors.
While I cannot reproduce it yet, I'll let you know when I can.
ipfs.log
Might be tied to this output on the console, or completely independent:
#6859
The text was updated successfully, but these errors were encountered: