touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #87202
[Bug 1469105] Re: Debug process and locate timeouts should be config parameters, not hardcoded
Changing status to "Won't Fix" as the linked branch changes were
reverted. It has been decided that we should rather disable timeouts
altogether in debug mode, rather than just using lenient timeouts.
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Won't Fix
--
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/1469105
Title:
Debug process and locate timeouts should be config parameters, not
hardcoded
Status in unity-scopes-api package in Ubuntu:
Won't Fix
Bug description:
The process timeout and locate timeouts in debug mode are currently
hardcoded in the source to 30s. These should be moved to
"Debug.Process.Timeout" in the registry config, and a
"Debug.Locate.Timeout" in the ZMQ config.
Doxygen doc and/or CONFIGFILES should also be updated as appropriate.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469105/+subscriptions
References