Replying to Avatar wuwei

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 most people are not really able to use nostrocket for very much. It's only really applicable to a few people at this stage because it takes a lot of time and effort to understand what it is and even more to get involved.

Solution: start adding problems nested under this one when it relates to the implementation and UX of Spaceman, Engine, the Relay, etc.

Whenever logging a problem, think: does solving this problem make bring Nostrocket closer to another participant getting involved?
Avatar
gsovereignty 2y ago

Problem: invalid memory address or nil pointer dereference in eventcatcher.go:88

```

panic: runtime error: invalid memory address or nil pointer dereference

[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102b89298]

goroutine 37 [running]:

nostrocket/messaging/eventcatcher.SubscribeToTree(0x1400023c120, 0x1400008e300, 0x1400023c0c0)

/Users/g/nostrocket_repo/engine/messaging/eventcatcher/eventcatcher.go:88 +0x3c8

created by nostrocket/messaging/eventconductor.handleEvents

/Users/g/nostrocket_repo/engine/messaging/eventconductor/eventconductor.go:64 +0x170

exit status 2

make: *** [reset] Error 1

```

Reply to this note

Please Login to reply.

Discussion

No replies yet.