Hey Christian, I think I can make it until the 28th, if we have consensus on how to fix this respectively if this is a bug at all.
Cheers t3sserakt -------- Forwarded Message -------- Subject: [GNUnet 0005597]: Deadlock for non reliable channel in case of missing message Date: Sun, 24 Feb 2019 21:49:57 +0100 From: Mantis Bug Tracker <[email protected]> To: [email protected] A NOTE has been added to this issue. ---------------------------------------------------------------------- (0014021) Christian Grothoff (manager) - 2019-02-24 21:49 https://bugs.gnunet.org/view.php?id=5597#c14021 ---------------------------------------------------------------------- 4 was hard-coded to make exactly these types of errors easier to spot for now. Later it should indeed be either adaptive, configurable, or both. I agree it makes no sense to drop a messsage in favor of an even older message. For unreliable channels, I think the desired behavior should be to queue the most recent THRESHOLD (=4, for now) messages. Can you fix this very soon (as in, before 28.2?) ----------------------------------------------------------------------
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
