Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 400482

Summary: Problems connecting and disconnecting drives
Product: [ECD] Orion Reporter: Anton McConville <antonm>
Component: ClientAssignee: Anton McConville <antonm>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: john.arthorne
Version: unspecifiedFlags: antonm: review? (susan)
Target Milestone: 2.0 RC2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Anton McConville CLA 2013-02-11 14:56:50 EST
In my haste to fix the saving of multiple drives on Friday, I learned by testing drives more thoroughly today that I had broken connecting and disconnecting drives.
Comment 1 Anton McConville CLA 2013-02-11 14:59:42 EST
There's a branch called DriveFixes
Comment 2 Susan McCourt CLA 2013-02-12 15:45:58 EST
Anton and I have spent the better part of a day on this issue, with several iterations of commits.

Things are definitely working better, in that you can connect drives now.  However, I observe some strange behavior.

1) the browser wants to remember the credentials prompt, so at times you don't get credentials prompting on connect, and if the tree does not refresh, you have no idea something happened.  
2) the *first time* I add a drive to a project, and try to connect, the drives tree never refreshes.  If I disconnect and reconnect, then the tree refreshes.  If I disconnect, reload the page, and connect, the tree refreshes.
3) It seems that once a drive is in a project, and has successfully connected, it behaves okay.  I'm not sure if it would behave properly if you pushed connect multiple times, etc.  It seems brittle.
4) If you use a port other than the default (mine was 2222), things seem to break down quickly.  There was a short time where I was able to see my drive with the alternate port.  But when I fetched the latest code and tried it, I was never able to connect to my ftp drive.  And...as soon as I tried to connect to it, subsequent calls to load the workspace would fail (from the nav page and the projects page).  Teammates observed that their workspace calls failed too.  FWIW, I *can* successfully import from this same site using the SFTP dialog.  So I know orion can talk to this server on port 2222, but maybe the drive API is having a problem with it.  It's very disconcerting that me adding a drive can hose the server for everyone else.

At this point, Anton is not observing (2) on his installation.  He is able to add a new drive, connect, and see the tree refresh.

We've determined that since we need to get to the bottom of this, and since Projects will not be linked in RC2, Anton can push what he has and work with John further on the workspace hang/port issue.
Comment 3 Susan McCourt CLA 2013-02-14 14:24:39 EST
Talked to John.  We understand some of the nature of the problems here.  There is a server bug and some client bugs to be worked through later, I'll link to them here.
Comment 4 Susan McCourt CLA 2013-02-14 14:41:23 EST
server problem is bug 400842.
not cleaning up drives is bug 400843.
Having UI for drive maintenance is bug 400844.