Damus
wuwei · 170w
Problem: nostrocket is not currently applicable to more than a few people The nostrocket implementation is currently lacking most of the features that are described in the unprotocol. This means mos...
gsovereignty profile picture
Problem: deadlock in consensus handler

```
Previous place where the lock was grabbed
goroutine 22 lock 0xc0005259f0
engine/library/debug.go:9 library.ValidateSaneExecutionTime { mu.Lock() } <<<<<
~/go/pkg/mod/github.com/sasha-s/[email protected]/deadlock.go:84 go-deadlock.(*Mutex).Lock { func (m *Mutex) Lock() { }
messaging/eventconductor/eventconductor.go:180 eventconductor.processStateChangeEventOutOfConsensus { sane := library.ValidateSaneExecutionTime() }
engine/library/eventStack.go:40 library.(*Stack).Pop { func (q *Stack) Pop() (*nostr.Event, bool) { }

Have been trying to lock it again for more than 1m0s
goroutine 109670 lock 0xc0005259f0
engine/library/debug.go:11 library.ValidateSaneExecutionTime.func1 { mu.Lock() } <<<<<
~/go/pkg/mod/github.com/sasha-s/[email protected]/deadlock.go:84 go-deadlock.(*Mutex).Lock { func (m *Mutex) Lock() { }

Here is what goroutine 22 doing now
goroutine 22 [chan send (nil chan), 1 minutes]:
nostrocket/state/consensustree.HandleConsensusEvent({{0xc000ab0dc0, 0x40}, {0xc000ab0180, 0x40}, 0x64e1b412, 0x9c401, {0xc0015ef6b0, 0x2, 0x2}, {0xc0010c4b80, ...}, ...}, ...)
/Users/g/git/nostrocket/fresh/engine/state/consensustree/newHandler.go:48 +0x328
nostrocket/messaging/eventconductor.processStateChangeEventOutOfConsensus(0xc0015303f0)
/Users/g/git/nostrocket/fresh/engine/messaging/eventconductor/eventconductor.go:191 +0x285
nostrocket/messaging/eventconductor.handleEvents()
/Users/g/git/nostrocket/fresh/engine/messaging/eventconductor/eventconductor.go:142 +0xd14
created by nostrocket/messaging/eventconductor.Start in goroutine 1
/Users/g/git/nostrocket/fresh/engine/messaging/eventconductor/eventconductor.go:52 +0x471

exit status 2
make: *** [reset] Error 1

```
1
gsovereignty · 163w
I'm closing [Problem: deadlock in consensus handler] on the nostrocket problem tracker, it's been resolved or become obsolete.