Ticket #1 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Stream tubes intermittently fail

Reported by: bmayton Owned by: plunkett
Priority: critical Milestone: 1.0 Release
Component: Networking Version: 1.0 beta 1
Keywords: Cc:

Description (last modified by bmayton) (diff)

When using the mesh network, stream tubes intermittently don't work. As a result, the deck transfer fails and the activity sits at the splash screen.

This is noted on the  Release notes for 8.1.1, in reference to the Read activity not reliably sharing PDFs.

This issue needs to be investigated, and we should either open a ticket on the laptop.org Trac or add our own observations to a current one, if it exists.

Change History

Changed 4 years ago by bmayton

  • description modified (diff)

Changed 4 years ago by bmayton

There has been at least some development on Sugar since we last tested this; we should upgrade laptops to the most recent build and verify that this issue still exists; if it does, we probably just need to buckle down, get the source code, and see if we can figure out what's going on. This is a pretty critical issue for our app (and the OLPC community at large would benefit from a fix to this!)

Changed 4 years ago by plunkett

Initial test runs of CPXO using candidate-765 of Sugar did not exhibit this issue. We won't know for sure whether the newer software has fixed this problem until we run more networking tests (by using CPXO more) and with more XOs.

Changed 4 years ago by plunkett

  • status changed from new to accepted

Changed 4 years ago by bmayton

We should set up an evening to get all of our XOs together and do some more testing on this to see if it's truly resolved. I've got an extra XO (so we should have a total of 5 that we can test with...)

Changed 3 years ago by plunkett

  • status changed from accepted to closed
  • resolution set to fixed

We've run several successful tests over the mesh network with 7-9 XOs. Only one OS exception arose (dbus exception), and this sort of intermittent problem will be dealt with by  Ticket 21. The most important thing is that the consistent download error we got last year over the mesh network is gone, so we can safely close this ticket.

Note: See TracTickets for help on using tickets.