| 2010-11-26 14:42:48 |
Gordon Tyler |
description |
If I click the Refresh button for a bzr branch which has a remote parent/submit branch, but my network has gone down, then the bzr explorer window becomes unresponsive for a minute or two until the connection attempt times out. It then displays a somewhat unfriendly error in a dialog and offers to Ignore or Close.
Network flakiness and timeouts are a fact of life. bzr explorer should handle them more gracefully. |
If I click the Refresh button for a bzr branch which has a remote parent/submit branch, but my network has gone down, then the bzr explorer window becomes unresponsive for a minute or two until the connection attempt times out. It then displays a somewhat unfriendly error in a dialog and offers to Ignore or Close. Since refreshes happen automatically when certain operations are performed, this unresponsiveness can happen unexpectedly.
Network flakiness and timeouts are a fact of life. bzr explorer should handle them more gracefully, possibly by displaying a "please wait" dialog and executing the command in the background so that it doesn't block the GUI thread.
|
|
