Skip to content
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

panic: runtime error: invalid memory address or nil pointer dereference #10459

Closed
3 tasks done
hsn10 opened this issue Jul 21, 2024 · 0 comments · Fixed by #10473
Closed
3 tasks done

panic: runtime error: invalid memory address or nil pointer dereference #10459

hsn10 opened this issue Jul 21, 2024 · 0 comments · Fixed by #10473
Assignees
Labels
dif/easy effort/hours Estimated to take one or several hours kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up

Comments

@hsn10
Copy link

hsn10 commented Jul 21, 2024

Checklist

Installation method

third-party binary

Version

0.29.0

Config

No response

Description

ERROR cmd/ipfs        kubo/daemon.go:595      failed to access config: cannot access config, repo not open
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x1b0 pc=0x1bd9aca]

goroutine 9480 [running]:
github.com/ipfs/kubo/cmd/ipfs/kubo.daemonFunc.func7()
        github.com/ipfs/kubo@v0.29.0/cmd/ipfs/kubo/daemon.go:597 +0xaa
created by time.goFunc
        time/sleep.go:177 +0x2d

its bug in demon.go. you print error message but use returned value nil anyway

@hsn10 hsn10 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Jul 21, 2024
@lidel lidel added effort/hours Estimated to take one or several hours dif/easy and removed need/triage Needs initial labeling and prioritization labels Aug 8, 2024
@lidel lidel self-assigned this Aug 8, 2024
@lidel lidel added the P1 High: Likely tackled by core team if no one steps up label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/easy effort/hours Estimated to take one or several hours kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants