Community
Participate
Working Groups
If I have a connection to a repository which is not accessible, over time my progress view fills with messages of the form: ERROR: Fetching CVS revision history : Cannot locate host I'm not sure how we should deal with this case. Some possibilities are: - allow user to explicitely disable the connection (i.e. it's still there but inactive) - remember that the message has been shown once (with not successes in between) - ...
This is compounded by all the extras we've added in the background (refresh, history view/editor linking, quickdiff). We need a way to turn off all these features when a connection is not possible. Possible approaches are to 1) turn off all auto-connections after a user specified number of failed connections. 2) prompt the user on a failed connection and allow them to explicitly disable auto-connection for that location. We also need a way to re-enable the location. Possibilites include: 1) re-enable on startup. 2) re-enable on next successful connection 3) re-enable in repositories view
If the performance hit is not too bad, you could optimistically try the operation each time, but remember not to complain to the user if it is failing. The problem with this approach is that the user needs *some* kind of feedback that they are disconnected. You also still have to notify him when operations that he explicitely generates fail.
Post 3.0
We have several issues relating to working disconnected that we should consider for 3.3.
We didn't have time to address this in 3.3.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
