I am probably not, now that you mention it... Updating groupchat updates gnunet-nim, but that doesn't have any sort of dependency check regarding GNUnet's installed version, so that's probably it.
Thanks for the quick response! On Mon, Jul 29, 2019, 23:40 Christian Grothoff <[email protected]> wrote: > Hi! > > I admittedly didn't test it, but the change looked fine to me. Are you > sure you're using the latest GNUnet? > > -Christian > > On 7/30/19 12:22 AM, Marcos Marado wrote: > > Hi, > > > > I haven't had time to debug this too much, but either gunet-nim's latest > > commit, > > "removed cadet option"[1], is buggy, or at least the only good example I > > know > > of it (groupchat) needs to be updated to work with it. > > > > With that commit on gnunet-nim, groupchat's client will get a server > message > > without data, and enter this 'if not' clause: > > > > proc processServerMessages(channel: ref CadetChannel, tui: Tui) > {.async.} = > > while true: > > let (hasData, message) = await channel.messages.read() > > if not hasData: > > shutdownGnunetApplication() > > > > [1] > > > https://git.gnunet.org/gnunet-nim.git/commit/?id=38c51715cfe0b2c6cdc662cffcc8de2eec8d28a9 > > > > Best regards, > > -- > > Marcos Marado > > > > _______________________________________________ > > GNUnet-developers mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/gnunet-developers > > > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers >
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
