After the weekend, the refreshing icon flashes

[GoogleCodeExporter]

I was running Eclipse in the debugger and it was stopped at a breakpoint all 
weekend. Unfortunately the mount point where some of my WM tasks were went 
offline. When I came in this morning I "resumed" the breakpoint and there was a 
workspace mechanic error, "Couldn't parse file".

After I ack'ed the error, the workspace mechanic icon flashed between the green 
check and the "refreshing" icon about 25 times. 

IMO, that's the bug.

The error log shows repeated attempts of the WM to connect to the missing file 
over the weekend (sometimes multiple times per minute, although this might be a 
logging artifact and not the actual behavior.)

I can provide more details offline.

Original issue reported on code.google.com by davidpl...@google.com on 11 Apr 2011 at 2:46

[GoogleCodeExporter]

Sorry, title should be "After the weekend, the refreshing icon flashes"

Original comment by davidpl...@google.com on 11 Apr 2011 at 2:47

[GoogleCodeExporter]

Original comment by konigsb...@gmail.com on 11 Apr 2011 at 2:49

• Changed title: After the weekend, the refreshing icon flashes
• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

David, I don't remember much about this. What do you propose as a solution?

Original comment by konigsb...@gmail.com on 9 Oct 2011 at 2:57

[GoogleCodeExporter]

Maybe something like, don't start the next update if there's already an
update "in progress"?  In this case, with NFS gone, there was no way for it
to recover without human intervention. In the case of certain errors like
this maybe an exponential backoff makes more sense than a straight period
schedule.

On Sat, Oct 8, 2011 at 10:58 PM, <
workspacemechanic.eclipselabs.org@codespot.com> wrote:

Original comment by davidpl...@google.com on 9 Oct 2011 at 2:03