Unreachable smartscopesproxy causes timeout exception in the client

Bug #1324138 reported by Paweł Stołowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-scopes-api (Ubuntu)
Triaged
Low
Marcus Tomlinson

Bug Description

If scopesregistry is configured to use smartscopesproxy, but smartscopesproxy is not running, then running a client such as unity-scope-tool results in a 300 ms timeout exception both in scopesregistry and in the client, and even local scopes are not available.

Related branches

Changed in unity-scopes-api:
assignee: nobody → Marcus Tomlinson (marcustomlinson)
Changed in unity-scopes-api:
status: New → In Progress
affects: unity-scopes-api → unity-scopes-api (Ubuntu)
Changed in unity-scopes-api (Ubuntu):
status: In Progress → Triaged
Changed in unity-scopes-api (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.