Peter
Peter
Re-opening the issue #120 as it hasn't been solved yet. The original author @dvc94ch [seems to open and close issues because it fits his workflow](https://github.com/dalek-cryptography/ed25519-dalek/issues/162#issuecomment-938157591). The original text: @dvc94ch wrote...
When we leave injector running for a long time, it starts to accumulate memory allocations and eventually crashes. Not sure yet whether the leak is in GNUnet, gnunet-channels, IPFS, ipfs-cache...
At the moment, when the injector receives a message from the origin, [it only checks the error code](https://github.com/equalitie/ouinet/blob/3a98a6b4053341118de7d94ccbdbc0da791ba608/src/injector.cpp#L112). But this error code has nothing to do with the response [HTTP...
Hi @moritz-wundke, I see you've made recently some changes here and it reminded me that I wanted to propose this for some time: I think the project suffers from the...
Hi @moritz-wundke. It seems the repository is becoming quite hairy. Perhaps some of us could help you with merging? One option would be that some of us would start merging...
It seems g++ 4.8 doesn't support some `random` features that the echo_chamber is using. ``` /home/ubuntu/np1sec/test/echo_chamber/tests.cc:547:10: error: ‘random_device’ in namespace ‘std’ does not name a type std::random_device rd; (16:28:01) donncha:...
`conversation.cc:1653: bool np1sec::Conversation::fsck(): Assertion `*user_it != event_it' failed.` This assertion fires when running the tests in tests/echo_chamber/tests.cc. Unfortunately, the particular test it happens in is random and the best chance...
This bug is exposed by the [test_session_join_order](https://github.com/equalitie/np1sec/blob/tests/test/echo_chamber/tests.cc#L371) test. The pseudo algorithm that the test implements goes like this: * user0 waits for user1 and user2 to enter the room. *...
Happens when a new client connects to the server with a name already present on the server. Say we have two clients Alice and Bob and they both log into...
It causes double free of Conversations inside ConversationList. We do mention that we can't call any room modifiers from inside Room's callbacks, but this is a bit different as the...