touch-packages team mailing list archive

[Pawel Stolowski <1540876@xxxxxxxxxxxxxxxxxx>]

<pstolowski> michi, can we count the number of pushes on the sender, and carry this number with finished message? or isn't 'finished' a real message?
<michi> Finished is a real message.
<michi> I’m not sure I follow your reasoning. Can you explain?
<michi> We count the number of pushes from the sender. Easy. Then what?
<michi> Send it with the finished message?
<michi> I guess that would allow the receiver to detect an overrun.
<pstolowski> michi, yes, that's the idea
<michi> Hmmm...
<michi> It would work in principle for error detection.
<michi> I’m not sure how easy it would be to implement down at the zmq level.
<michi> Because it’s stateful but, at the zmq level, we are currently stateless.
<michi> Not impossible, but possibly ugly.
<michi> It’s worth thinking about though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1540876

Title:
  Not all results recieved when there is a lot of them (>=3000?)

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  It looks like ZMQ high water-mark limits the number of results that
  can succesfuly be received by a client to something around 2000; this
  may depend on the result size and delays between pushes though. With
  3000 results in my test code I was receiving approximately 1900, the
  remainder was dropped on the floor. While these numbers are probably
  more than we will ever need, it may be worth looking into it. Perhaps
  ZMQ queue size can be increased, also a meaningful error in the logs
  about hitting such cases would be nice (if possible at all).

  I'll add a pointer to a sample test case from unity-scopes-shell at a
  later time, please contact me if I forget to do so ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1540876/+subscriptions