Hello Baptiste, Yes, even though the last version of OpenDHT is not yet used in Ring nighlies, the issue have been fixed in the OpenDHT master and it should be safe to update.
Regards and happy new year, Adrien From: "Baptiste Jonglez" <[email protected]> To: [email protected] Sent: Friday, January 1, 2016 1:12:24 PM Subject: Re: [Ring] Important: update your Ring Hi, Did you find out what the issue was? Is it safe to update to a newer version of OpenDHT? Thanks! Baptiste On Sat, Dec 12, 2015 at 10:29:29AM -0500, Stepan Salenikovich wrote: > We reverted to openDHT commit 184dc17aa8cf57a9a3e1b26ff2794b2cab4597ba > in this patch: https://gerrit-sflphone.savoirfairelinux.com/#/c/3280/ > > The two openDHT bumps in ring-daemon that seemed to cause problems were to > 2842f45cbdddbb0be66840d6550c6a277995dfe0 and > 9a301569a49faaebfbb8ab09d47bab5772e5c618 > > 0a4195ae08f7fb1a7a215eb0e7542f9ad33ca80d is before > 2842f45cbdddbb0be66840d6550c6a277995dfe0 > > however it is after the commit that we reverted to, so you may want to > downgrade your maintained version until we figure out what the issue is in > openHDT > > -stepan > > ----- Original Message ----- > From: "Baptiste Jonglez" <[email protected]> > To: [email protected] > Sent: Saturday, December 12, 2015 5:53:10 AM > Subject: Re: [Ring] Important: update your Ring > > Hi, > > Do you have any idea of the incriminating commit in opendht, and/or > conditions in which this bug triggers? Is it purely caused by opendht, or > does it depend on the version of ring? > > On Archlinux, the current version of the opendht package I maintain is > 0a4195ae08f7fb1a7a215eb0e7542f9ad33ca80d, and a user reported a similar > issue. But it does not trigger on my system. > > Thanks, > Baptiste > > On Thu, Dec 10, 2015 at 07:01:10PM -0500, Guillaume Roguez wrote: > > Hi, > > > > We've found that a recent version of our DHT library may cause some > > hi-traffic on your network and may saturate your computer ressources. > > > > We've solved the problem on Ring by reverting to an older version (of > > OpenDHT) to not introduce this regression, until we found the exact issue. > > The problems has not been seen with this fix so we recommand, if you have > > updated Ring during the day of 10 december, update it now as > > our recent builds have the fix. > > > > Thanks, > > Guillaume > > Ring Project Director > > _______________________________________________ > > Ring mailing list > > [email protected] > > https://lists.savoirfairelinux.net/mailman/listinfo/ring > > _______________________________________________ > Ring mailing list > [email protected] > https://lists.savoirfairelinux.net/mailman/listinfo/ring > _______________________________________________ > Ring mailing list > [email protected] > https://lists.savoirfairelinux.net/mailman/listinfo/ring _______________________________________________ Ring mailing list [email protected] https://lists.savoirfairelinux.net/mailman/listinfo/ring
_______________________________________________ Ring mailing list [email protected] https://lists.savoirfairelinux.net/mailman/listinfo/ring
