Public bug reported:

The client can timeout while the daemon is still doing a lot of active
work.

There are 3 cases to take into account:
- daemon not started: give a timeout for the daemon to start before the client 
exits. Ideally, we would pulse back to the client, but the entrypoint isn’t 
reached out yet
- once the call starts:
 If other calls are in progress and there is mutex, ideally pulse it to the 
client (or give a new timeout)
- when it’s our turn:
the pulse to the daemon can be done by the log progress which we will thus 
always send to the client.

Note that if we wait for too long, we can imagine a pulsing progress bar
on the CLI with which steps we are at.

This needs to change GRPC messages back but will drastically reduce
timeouts that people can get when having a lot of datasets or in code
path we didn’t optimize yet.

** Affects: zsys (Ubuntu)
     Importance: High
         Status: Triaged

** Changed in: zsys (Ubuntu)
       Status: New => Triaged

** Changed in: zsys (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1875564

Title:
  Enhance timeout handling to avoid error rpc error: code =
  DeadlineExceeded desc = context deadline exceeded while the daemon is
  doing work

Status in zsys package in Ubuntu:
  Triaged

Bug description:
  The client can timeout while the daemon is still doing a lot of active
  work.

  There are 3 cases to take into account:
  - daemon not started: give a timeout for the daemon to start before the 
client exits. Ideally, we would pulse back to the client, but the entrypoint 
isn’t reached out yet
  - once the call starts:
   If other calls are in progress and there is mutex, ideally pulse it to the 
client (or give a new timeout)
  - when it’s our turn:
  the pulse to the daemon can be done by the log progress which we will thus 
always send to the client.

  Note that if we wait for too long, we can imagine a pulsing progress
  bar on the CLI with which steps we are at.

  This needs to change GRPC messages back but will drastically reduce
  timeouts that people can get when having a lot of datasets or in code
  path we didn’t optimize yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1875564/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to