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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悶 github.com/dagger/dagger/dagql/idtui.CollectSpan
invalid memory address or nil pointer dereference
#7192
Labels
kind/bug
Something isn't working
Comments
x-linking to #7227 - this should at least stop the panic. |
Just hit this on dagger call lint stdout
...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4b pc=0xf436bd]
goroutine 1 [running]:
github.com/dagger/dagger/dagql/idtui.CollectSpans(0xc0004660c0, {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...})
/app/dagql/idtui/types.go:52 +0x41d
github.com/dagger/dagger/dagql/idtui.(*Frontend).recalculateView(0xc000468000)
/app/dagql/idtui/frontend.go:[39](https://github.com/dagger/dagger/actions/runs/8986651161/job/24683291279#step:4:40)5 +0x33
github.com/dagger/dagger/dagql/idtui.(*Frontend).finalRender(0xc000468000)
/app/dagql/idtui/frontend.go:217 +0xa5
github.com/dagger/dagger/dagql/idtui.(*Frontend).Run(0xc000468000, {0x1[41](https://github.com/dagger/dagger/actions/runs/8986651161/job/24683291279#step:4:42)98b0, 0x1d6d680}, 0x12e3fd8)
/app/dagql/idtui/frontend.go:131 +0xe5
main.main()
/app/cmd/dagger/main.go:225 +0xac
Error: exit status 2
exit status 1 For now, just re-running. Looking forward to trying out #7227 when cc @matipan |
This was referenced May 7, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue?
We've hit this error a few times in https://github.com/dagger/dagger/actions/runs/8821414426/job/24217223788?pr=7082, part of:
Just in case those logs become unavailable, I am attaching them as
zip
: logs_23113975550.zipcc @vito
Dagger version
dagger v0.11.1 (registry.dagger.io/engine) linux/amd64
Steps to reproduce
No response
Log output
No response
The text was updated successfully, but these errors were encountered: