Community
Participate
Working Groups
I20030525 I setup my repository connection to use pserver for read access. When I now expand nodes in the CVS Repository view it still says: "Retrieving children - authenticating over extssh". Also, in the new Sync view when I click files (to compare) with outgoing changes they use extssh (or at least the dialog tells so).
Do you mean I20030925? I can't reproduce this. I also put a breakpoint in the ssh open connection and it's never called when read connection is configured.
Yes I20030925. I did not debug it. I only reported what I see in the UI (dialogs) maybe it's doing something else behind the back.
Note: it is really much faster (cool!). My PR is just about the dialog/status line. Maybe it is the first connection when it displays extssh (before redirecting)?
Saw this again today (have a witness :-). It seems to be reproducible by starting the workspace with sync view in the perspective and then clicking on some files (so that the compare editor opens - I use single-click mode).
Mike, you can look into this when we improve the read/write repo UI and support.
I suspect this has to do with the loading order of plugins. The read/write repo locations are stored in core but persisted by the UI (I know it doesn't make since but it was a lot simpler and cleaner to implement because the UI mechanism is XML based and the core one isn't). Anyway, if a connection was attempted before the UI had loaded and initialized it's settings, this behavior would occur. I will verify this when we improve the support of this feature.
*** Bug 44458 has been marked as a duplicate of this bug. ***
*** Bug 46541 has been marked as a duplicate of this bug. ***
Any change that this get fixed soon? Every time when starting my workspace and doing CVS reads (from the Team view) I first have to go to another view (e.g. Package Explorer) and do some CVS operation, otherwise it uses extsh and of course my time.
Were hoping that the user setting support will help us here so were waiting to see what the final incarnation of that is.
A manual workaround after the wrong connetion is used: - open the CVS Repositories view - edit the extssh connection - re-select the pserver for read - press OK
Now that I am using SSH2 (which works great) this is becoming a bigger pain: On startup the UI hangs waiting for my password for the SSH2 authentication. This gets caused by quick diff that accesses the repository. Though this is basically correct it shouldn't do this via SSH2 since I've setup anonymous repos for read access.
With the new SSH2 support, the intention was to remove the read/write configurability since SSH2 is faster due to connection reuse. However, we will also need to consider the case you just mentioned. We will look into this in M8.
>With the new SSH2 support, the intention was to remove the read/write >configurability since SSH2 is faster due to connection reuse. Faster than anonymous access using pserver?
Potentially, since the connection is only made once and all further communications are done over that channel. It's hard to say whether the cost of encrypting/decrypting the packets is more or less than the cost of opening a socket (or 2 or 3) for each project being refreshed. However, there is still quite a bit of work required to make the read/write location feature "real" so the tradeoff really involves whether we have the cycles to complete the feature properly since, at this point, it is not ready for a released product. This bug is actually the easiest part to fix. The complicated portion is how to surface the UI in a way that makes sense.
*** Bug 53765 has been marked as a duplicate of this bug. ***
Fix released to HEAD. The read/write locations are now stored in the instance preferences.
