| Summary: | [error handling] Quick diff fails when working offline - no route to host | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Randy Hudson <hudsonr> | ||||
| Component: | Text | Assignee: | Tom Hofmann <eclipse> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | christof_marti | ||||
| Version: | 3.0 | Keywords: | usability | ||||
| Target Milestone: | 3.1 M3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Randy Hudson
Is this major? The average user may not realize that the quickdiff feature is causing this connection attempt. IMO the workaround of disabling quickdiff is not too good. Yes, we talked about this at the end of the 3.0 cycle and wasn't able to address it. This is similar to the error with the scheduled synchronize. The error with scheduled synchronize occurs once every hour or more. The error with quick-diff occurs every time I open an editor. For example, when looking at search results, debugging, using F3. Can you consider fixing this for 3.0.2? Maybe, but I'll fix in 3.1 first since they don't want us to submit fixes to the maintenance stream just yet. I have a solution to this. I will attach a patch and forward to Text once I have added the relevant patches to bug 76726. Created attachment 15417 [details]
Patch to QuickDiff to not prompt the user on errors
Moving to Text. I have attached a patch that allows QuickDiff to signal to the Progress view not to prompt on error but instead to give visual indication in the status bar that an error has occurred. Applied, thanks. Available in builds >20041028. May be considered for 3.0.2. Since the fix for bug 76726 is marked M3, I don't think we will do anything for 3.0.2 for this - comments? Closing. OK. Verified in I200411022000 I am still getting entries in my log for this problem, but the dialog doesn't appear anymore. Should I open a separate bug? IMO you should file a request against team - connection problems should not be reported as errors. |