[Sugar-devel] [RELEASE] Sugar 0.113 unstable

[James Cameron]

I got bored with this and went on to other things.

If anyone else is interested in working on the collaboration stack,
let me know.

On Wed, Mar 20, 2019 at 07:47:57PM +1100, James Cameron wrote:
> I've heard nothing back on your issue.
> 
> I was able to reproduce a hesitancy in collaboration using Salut over
> a routed network.
> 
> Tracing showed that the mDNS packets to express learner presence were
> being transmitted (per tcpdump), but not all received (again per
> tcpdump).
> 
> Here's a simple Python script to reproduce that.  On one system, run
> "tcpdump -s 0 -w file port 5354", and on the other system run the
> script.
> 
> 
> import socket
> import time
> socket = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
> socket.bind(('224.0.0.32', 5354))
> for n in range(200):
>     socket.sendto('0' * 300, ('224.0.0.32', 5354))
>     time.sleep(0.1)
> 
> 
> After the test, interrupt tcpdump and observe the packet count shown.
> 
> My observations were 0% packet loss on wired network, and about 50%
> packet loss where the last hop was infrastructure wireless on an
> isolated network.  Compared with 0% ping loss with "ping -i 0.1 -n -c
> 200".
> 
> This result for multicast UDP packets is astoundingly bad, and
> suggests something has changed with respect to multicast UDP handling,
> but I've not got to the bottom of it yet.
> 
> So few applications depend on multicast UDP, that Sugar collaboration
> over Salut can be a bit of a Miner's canary.
> 
> Both test systems were running Ubuntu 18.04.
> 
> On Sat, Mar 16, 2019 at 02:17:53PM +1100, James Cameron wrote:
> > Your logs show one of the problems fixed in 0.113; the "Error parsing
> > public key".  Please test with 0.113, thanks.
> > 
> > Also, please capture a complete set of your problem data, and try to
> > concentrate the information into one place; the reports are too
> > scattered and conflicting; may I suggest;
> > 
> > - what was done to reproduce,
> > 
> > - what was expected and what was observed,
> > 
> > - is it over a link-local network, a routed network, or via
> >   jabber.sugarlabs.org,
> > 
> > - if link-local, is im.telepathy.MissionControl.FromEmpathy use-conn
> >   false?
> > 
> > - add Telepathy debugging,
> >   https://wiki.sugarlabs.org/go/BugSquad/Telepathy_Debugging
> > 
> > - use dbus-monitor,
> >   http://lists.sugarlabs.org/archive/sugar-devel/2019-March/056365.html
> > 
> > No, I don't think this problem should delay 0.114, as it does not seem
> > likely to be caused by Sugar.
> > 
> > On Fri, Mar 15, 2019 at 07:54:46PM -0700, Alex Perez wrote:
> > > James,
> > > 
> > > Apologies for the thread hijacking, but I feel it's appropriate...
> > > 
> > > FYI, I have just discovered that collaboration in Sugar under 0.112 + Ubuntu
> > > 19.04 is also broken. We must get this fixed before we can release the stable
> > > 0.114.
> > > 
> > > See [1]https://termbin.com/qtkh
> > > 
> > > James Cameron wrote on 3/15/2019 7:51 PM:
> > > 
> > >     Sorry, I don't know.  I've not done that.  So many things would go
> > >     wrong.  You ought to wait for Fedora project to package Sugar 0.113.
> > > 
> > >     I'm testing on Ubuntu 18.04 at the moment, and it seems okay after
> > >     fixing those two errata in my previous post to this thread.
> > > 
> > > References:
> > > 
> > > [1] https://termbin.com/qtkh
> > 
> > -- 
> > James Cameron
> > http://quozl.netrek.org/
> 
> -- 
> James Cameron
> http://quozl.netrek.org/

-- 
James Cameron
http://quozl.netrek.org/