@hector I don’t know if I just found a bug or not but wanted you to take a quick look to see if I really should open an issue on Git.
I used a custom connector as I said before, and everything seemed to be working until I tried to bootstrap the peer to another one. It would bootstrap and after 5 seconds It would throw a panic error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x4f44886]
goroutine 22381 [running]:
github.com/ipfs/ipfs-cluster.(*Cluster).Peers(0xc0006fa000, 0x5810ba0, 0xc0039d0120, 0x0, 0x0, 0x0)
/Users/mosanoteam/go/pkg/mod/github.com/ipfs/ipfs-cluster@v0.13.0/cluster.go:1579 +0x136
main.startCluster.func1(0x5810ba0, 0xc0039d0120, 0x0, 0x0, 0x2f40)
/Users/mosanoteam/go/src/github.com/PZenha/poc-ipfs-cluster/main.go:497 +0x3e
main.(*Connector).ConnectSwarms(0xc000e21ca0, 0x5810ba0, 0xc0039d0120, 0x0, 0x40624d1)
/Users/mosanoteam/go/src/github.com/PZenha/poc-ipfs-cluster/connector.go:100 +0x5c
github.com/ipfs/ipfs-cluster.(*Cluster).Join.func2()
/Users/mosanoteam/go/pkg/mod/github.com/ipfs/ipfs-cluster@v0.13.0/cluster.go:974 +0x4b
created by time.goFunc
/usr/local/Cellar/go/1.13.7/libexec/src/time/sleep.go:168 +0x44
exit status 2
The problem seems to be from the function
func (c *Cluster) Peers(ctx context.Context) []*api.ID {...}
It was originally called like this:
connector, err := NewConnector(GetNode(), func(ctx context.Context) *capi.ID {
return c.Peers(ctx)
})
And instead of using the Peers method from the Cluster struct I used the Peers function from the Rest API as a work around and works fine.
Do you think this might be a problem from the lib worth of opening an issue?