Bug 210898 - Be more resilient when one team repo connection fails
Summary: Be more resilient when one team repo connection fails
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-11-26 03:44 EST by Philipe Mulet CLA
Modified: 2019-09-06 16:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2007-11-26 03:44:15 EST
Build 3.4m3

Currently, when synchronizing a workspace using multiple team repo connections, if any connection is causing a failure (like authentication problem), then a dialog opens to fix it, but if unable to do so (like need system admin to reset account) then the only left choice is CANCEL.

Problem is that CANCEL is cancelling the entire workspace synchronization, not just this team connection... being more resilient, I could still synchronize the rest of the workspace, with an indication that some portions weren't updated.
Comment 1 Tomasz Zarna CLA 2007-11-26 04:44:51 EST
Sounds like a good idea to me. Hitting "Cancel" on a dialog should only cancel a related connection and log a warning (or even an error) to the Error Log. I think collecting possible errors in a multi-status would do the job. In order to indicate that there are some resources which weren't updated we could also decorate those resource in some way in the Sync View. Any ideas?

Unfortunately, we don't have the manpower to address it at this time. Patches will be accepted.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:04:21 EDT
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.