touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #111609
[Bug 1502282] Re: "unknown" connectivity status problematic
Michi, have a look at http://bazaar.launchpad.net/~unity-team/unity-
scopes-shell/trunk/view/head:/src/Unity/scope.cpp#L745
The scope should actually never receive scopes::SearchMetadata::Unknown.
--
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/1502282
Title:
"unknown" connectivity status problematic
Status in The Savilerow project:
New
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
metadata provides a scope a network connectivity status enum with three possible states:
* connected
* disconnected
* unknown
Sometimes unknown is the current state. This is quite problematic
because in general a scopes that queries the network (that is, most
scopes) need to know whether there is network or is not network and
depending on this either make the network queries or display an error
message.
A status of unknown connectivity leaves the scope with no valid option:
* the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily
* the scope could assume the network is up, but this is dangerous if it is not up
To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions
References