We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Got this panic a few times now on my nodes running 0.2.1 and @frrist has seen it as well
panic: counter already signaled done. use a new counter. goroutine 16680219 [running]: github.com/ipfs/go-todocounter.(*todoCounter).Increment(0xc056d4eae0, 0xc000000001) /home/ubuntu/pkg/mod/github.com/ipfs/go-todocounter@v0.0.1/counter.go:86 +0xaf github.com/libp2p/go-libp2p-kad-dht.(*dhtQueryRunner).addPeerToQuery(0xc06ff17340, 0xc012deda40, 0x22) /home/ubuntu/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.0.4/query.go:200 +0x103 github.com/libp2p/go-libp2p-kad-dht.(*dhtQueryRunner).Run(0xc06ff17340, 0x1940bc0, 0xc073a03200, 0xc050a73650, 0x3, 0x3, 0x0, 0x0, 0x0) /home/ubuntu/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.0.4/query.go:136 +0x140 github.com/libp2p/go-libp2p-kad-dht.(*dhtQuery).Run(0xc050a736e0, 0x1940bc0, 0xc073a03200, 0xc050a73650, 0x3, 0x3, 0x0, 0x0, 0x0) /home/ubuntu/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.0.4/query.go:70 +0xff github.com/libp2p/go-libp2p-kad-dht.(*IpfsDHT).GetClosestPeers.func2(0xc07c088900, 0xc061d0d120, 0xc050a736e0, 0x1940c40, 0xc07d541980, 0xc050a73650, 0x3, 0x3, 0xc0437d37d0, 0x26) /home/ubuntu/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.0.4/lookup.go:96 +0xdb created by github.com/libp2p/go-libp2p-kad-dht.(*IpfsDHT).GetClosestPeers /home/ubuntu/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.0.4/lookup.go:92 +0x358
Related libp2p issue: libp2p/go-libp2p-kad-dht#292
We are currently on 0.0.4 of go-libp2p-kad-dht and we need to be on at least 0.0.5 (fixed in libp2p/go-libp2p-kad-dht#301)
0.0.4
go-libp2p-kad-dht
0.0.5
https://github.com/filecoin-project/go-filecoin/blob/d7c3b1df109b7d3e119302a02ba956ab75fa2bb2/go.mod#L51
The text was updated successfully, but these errors were encountered:
update to go-libp2p-kad-dht@v0.0.10
e0d5840
fixes #2753
027712e
9988899
update to go-libp2p-kad-dht@v0.0.8 (#2754)
6c0c004
update to go-libp2p-kad-dht@v0.0.8 - fixes #2753
frrist
Successfully merging a pull request may close this issue.
Got this panic a few times now on my nodes running 0.2.1 and @frrist has seen it as well
Related libp2p issue: libp2p/go-libp2p-kad-dht#292
We are currently on
0.0.4
ofgo-libp2p-kad-dht
and we need to be on at least0.0.5
(fixed in libp2p/go-libp2p-kad-dht#301)https://github.com/filecoin-project/go-filecoin/blob/d7c3b1df109b7d3e119302a02ba956ab75fa2bb2/go.mod#L51
The text was updated successfully, but these errors were encountered: