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: segfault in eventcatcher

```

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

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

goroutine 20 [running]:

nostrocket/messaging/eventcatcher.SubscribeToTree(0x1400008c120, 0x1400006a300, 0x1400008c0c0)

/Users/g/nostrocket_repo/engine/messaging/eventcatcher/eventcatcher.go:63 +0x354

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

Avatar
gsovereignty 2y ago

I'm closing problem c623d0daeb8ffb3675a606c7912ccf450e6034b161dc5aab099c0d58e927f629 on the nostrocket problem tracker, it's been resolved or become obsolete.

Avatar
gsovereignty 2y ago

[Problem: segfault in eventcatcher] on the nostrocket problem tracker was previously closed but I'm re-opening it because it appears that it isn't resolved.

Avatar
gsovereignty 2y ago

[Problem: segfault in eventcatcher] on the nostrocket problem tracker was previously closed but I'm re-opening it because it appears that it isn't resolved.

Avatar
gsovereignty 2y ago

Problem: don't know when system is sleeping

The segfault described by c623d0daeb8ffb3675a606c7912ccf450e6034b161dc5aab099c0d58e927f629 happens when the system goes to sleep.

There's nothing we can really do about it unless we know when the system is going to sleep.

Solution: use a C library to detect system sleep.

Avatar
gsovereignty 2y ago

I'm claiming [Problem: don't know when system is sleeping] on the nostrocket problem tracker so that I can work on it and other people don't duplicate my efforts.

Avatar
gsovereignty 2y ago

I'm closing [Problem: don't know when system is sleeping] on the nostrocket problem tracker, it's been resolved or become obsolete.

Avatar
gsovereignty 2y ago

I'm claiming [Problem: segfault in eventcatcher] on the nostrocket problem tracker so that I can work on it and other people don't duplicate my efforts.

Avatar
gsovereignty 2y ago

I'm closing [Problem: segfault in eventcatcher] on the nostrocket problem tracker, it's been resolved or become obsolete.