[Touch-packages] [Bug 1469069] Re: Two-way request for debug mode status should itself use a lenient timeout
** Changed in: unity-scopes-api (Ubuntu) Status: In Progress = Fix Released -- 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/1469069 Title: Two-way request for debug mode status should itself use a lenient timeout Status in unity-scopes-api package in Ubuntu: Fix Released Bug description: Upon determining whether a scope is in debug mode, the scope must be located via the registry. The registry rightfully allows the scope to startup slowly, but the originating locate() call enforces the regular timeout. This is causing premature timeout errors when trying debug a scope on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+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
[Touch-packages] [Bug 1469069] Re: Two-way request for debug mode status should itself use a lenient timeout
Reopening this bug as disabling the timeouts completely has been decided to be the better option than lenient timeouts in debug mode. ** Changed in: unity-scopes-api (Ubuntu) Status: Fix Committed = In Progress ** Branch linked: lp:~marcustomlinson/unity-scopes- api/disable_timeouts_in_debug_mode ** Branch unlinked: lp:~marcustomlinson/unity-scopes- api/fix_debug_mode_locate_timeout -- 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/1469069 Title: Two-way request for debug mode status should itself use a lenient timeout Status in unity-scopes-api package in Ubuntu: In Progress Bug description: Upon determining whether a scope is in debug mode, the scope must be located via the registry. The registry rightfully allows the scope to startup slowly, but the originating locate() call enforces the regular timeout. This is causing premature timeout errors when trying debug a scope on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+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
[Touch-packages] [Bug 1469069] Re: Two-way request for debug mode status should itself use a lenient timeout
** Changed in: unity-scopes-api (Ubuntu) Status: In Progress = Fix Committed -- 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/1469069 Title: Two-way request for debug mode status should itself use a lenient timeout Status in unity-scopes-api package in Ubuntu: Fix Committed Bug description: Upon determining whether a scope is in debug mode, the scope must be located via the registry. The registry rightfully allows the scope to startup slowly, but the originating locate() call enforces the regular timeout. This is causing premature timeout errors when trying debug a scope on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+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
[Touch-packages] [Bug 1469069] Re: Two-way request for debug mode status should itself use a lenient timeout
** Branch linked: lp:~marcustomlinson/unity-scopes- api/fix_debug_mode_locate_timeout -- 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/1469069 Title: Two-way request for debug mode status should itself use a lenient timeout Status in unity-scopes-api package in Ubuntu: In Progress Bug description: Upon determining whether a scope is in debug mode, the scope must be located via the registry. The registry rightfully allows the scope to startup slowly, but the originating locate() call enforces the regular timeout. This is causing premature timeout errors when trying debug a scope on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+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
[Touch-packages] [Bug 1469069] Re: Two-way request for debug mode status should itself use a lenient timeout
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided = High -- 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/1469069 Title: Two-way request for debug mode status should itself use a lenient timeout Status in unity-scopes-api package in Ubuntu: In Progress Bug description: Upon determining whether a scope is in debug mode, the scope must be located via the registry. The registry rightfully allows the scope to startup slowly, but the originating locate() call enforces the regular timeout. This is causing premature timeout errors when trying debug a scope on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+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