Hardcoded values found in scoperegistry.cpp and ZmqScope.cpp. Search for "30000".
** Description changed: 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. ** Summary changed: - Debug process timeout and locate timeouts should be config parameters rather than hardcoded into the source + Debug process and locate timeouts should be config parameters, not hardcoded -- 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: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
