Maiden sometimes segfaults on update -all #226
Description
Hi.
I am not totally sure if this is the place to report this, but I got following while running maiden project update --all
…
Updating: fiahod ... already up-to-date
Updating: fibonacci ... already up-to-date
Updating: firstlight ... already up-to-date
Updating: fixed-filter-banking-crisis ... panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x535ec8]
goroutine 1 [running]:
github.com/monome/maiden/pkg/dust.(*Project).UpdateMetaData(...)
/home/runner/work/maiden/maiden/pkg/dust/project.go:358
github.com/monome/maiden/pkg/dust.(*Project).Update(0x14201b0, 0x1, 0x0, 0x1418434, 0x1b, 0x0)
/home/runner/work/maiden/maiden/pkg/dust/project.go:398 +0x1e8
github.com/monome/maiden/cmd.updateProjectRun(0x1090248, 0x0, 0x1)
/home/runner/work/maiden/maiden/cmd/project.go:216 +0x258
github.com/monome/maiden/cmd.glob..func6(0xd6bdc0, 0x1090248, 0x0, 0x1)
/home/runner/work/maiden/maiden/cmd/project.go:49 +0x40
github.com/spf13/cobra.(*Command).execute(0xd6bdc0, 0x1090238, 0x1, 0x1, 0xd6bdc0, 0x1090238)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:766 +0x1e8
github.com/spf13/cobra.(*Command).ExecuteC(0xd6c280, 0x1102030, 0x0, 0x1)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:852 +0x230
github.com/spf13/cobra.(*Command).Execute(...)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:800
github.com/monome/maiden/cmd.Execute()
/home/runner/work/maiden/maiden/cmd/root.go:48 +0x20
main.main()
/home/runner/work/maiden/maiden/main.go:8 +0x14
I almost never run the update from command line, but somehow I now did and I get this. Could this be the reason that the update all scripts from the web interface relatively often stalls and does not complete?