[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Subclipse Hangs Eclipse Doing New Repository...

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-10-27 21:42:29 CEST

"Kenneth Evans, Jr." <evans@aps.anl.gov> wrote on 10/27/2006 03:24:28 PM:

> I didn't find this in the bugs. I was using Subclipse for the
first
> time with a repository of the form:
>
> svn+ssh://phoebus/home/phoebus/EVANS/svn/test
>
> This repository is working. On doing New Repository Location...
with
> this URL, it gave me a dialog indicating it was in progress. The dialog
> stayed up for more than 15 min. Then I pressed the Cancel button on the
> dialog. That gave me another dialog and an hourglass. It stayed that
way
> for another 10 min or so. I did not get a chance to get a screen
capture of
> the dialogs.
>
> So, it was hung. Normally, I would have had to kill Eclipse or
Java to
> get out of it. By chance, I had started Eclipse with java.exe, not
> javaw.exe, so I had a (Windows, not Eclipse) console. (I have been
> debugging another issue with Eclipse.) The console was obscured, but I
> thought I might do a Ctrl-Break and get a stack trace. On making the
> console visible, I saw it contained:
>
> The authenticity of host 'phoebus (111.222.333.444)' can't be
established.
> RSA key fingerprint is ff:ee:dd:cc:bb:aa:99:88:77:66:55:44:33:22:11:00.
> Are you sure you want to continue connecting (yes/no)?
>
> On saying yes, Eclipse unhung and the new repository action finished
(in
> spite of the Cancel). (And Subclipse worked OK after that, as well ;-)
> This message is a one-time message, so it should work from now on.

That is the expected behavior. See this page in the documentation:

http://svn.collab.net/subclipse/help/topic/org.tigris.subversion.subclipse.doc/html/reference/protocol.html

If you use a graphical SSH client like TortoisePlink, you would get a GUI
prompt.

> So, this is pretty user unfriendly. If I had been running Javaw as
is
> normally done, I would have had no idea what the problem was. I assume
> Subclipse is exec'ing the ssh command, and that ssh is writing to stdout
or
> stderr. IMHO what you should be doing is capturing these streams and
> sending them to the Eclipse console. And making sure Cancel kills the
exec
> process.

Subclipse has no role in the process. The Subversion API is running the
SSH client you have configured in your Subversion configuration area.

An alternative is to use the JavaSVN adapter, which uses a Java SSH
library. You will then get GUI prompts for things like this. It also
offers better performance for SSH because it maintains a persistent
session.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Oct 27 21:42:39 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.