You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Robert S. Sfeir" <yo...@gmail.com> on 2005/07/19 17:37:47 UTC
Major bug in svn command line client
This one bit me one too many times, but apparently we can now
reproduce this on OS X and Linux. Clients tested were 1.1.1, 1.1.4
and 1.2.0.
If you have OS X or Linux try this (At your own risk)
at the command line type:
svn co svn://codepuccino.com/
press enter
press ctrl + c to kill it since it's not the right port.
Watch the machine hang. On OSX I can no longer start any apps, and
rebooting is not possible either I have to force a shutdown and restart.
Can someone please triple confirm this?
Thanks
R
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by kf...@collab.net.
kfogel@collab.net writes:
> > at the command line type:
> >
> > svn co svn://codepuccino.com/
> >
> > press enter
> >
> > press ctrl + c to kill it since it's not the right port.
> >
> > Watch the machine hang. On OSX I can no longer start any apps, and
> > rebooting is not possible either I have to force a shutdown and
> > restart.
> >
> > Can someone please triple confirm this?
>
> The fact that Subversion hangs itself is a bug in Subversion. (I
> think it may be fixed in trunk code, though, see
> http://subversion.tigris.org/issues/show_bug.cgi?id=2297.)
I'm sorry, I stupidly didn't notice the "svn://", which means this
isn't issue #2297. Please ignore that part of my post.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by kf...@collab.net.
"Robert S. Sfeir" <yo...@gmail.com> writes:
> This one bit me one too many times, but apparently we can now
> reproduce this on OS X and Linux. Clients tested were 1.1.1, 1.1.4
> and 1.2.0.
>
> If you have OS X or Linux try this (At your own risk)
>
> at the command line type:
>
> svn co svn://codepuccino.com/
>
> press enter
>
> press ctrl + c to kill it since it's not the right port.
>
> Watch the machine hang. On OSX I can no longer start any apps, and
> rebooting is not possible either I have to force a shutdown and
> restart.
>
> Can someone please triple confirm this?
The fact that Subversion hangs itself is a bug in Subversion. (I
think it may be fixed in trunk code, though, see
http://subversion.tigris.org/issues/show_bug.cgi?id=2297.)
The fact that it hangs your *machine* is a bug in OS X :-), however.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by Saulius Grazulis <gr...@akl.lt>.
On Tuesday 19 July 2005 20:37, Robert S. Sfeir wrote:
> If you have OS X or Linux try this (At your own risk)
>
> at the command line type:
>
> svn co svn://codepuccino.com/
>
> press enter
>
> press ctrl + c to kill it since it's not the right port.
>
> Watch the machine hang. On OSX I can no longer start any apps, and
> rebooting is not possible either I have to force a shutdown and restart.
>
> Can someone please triple confirm this?
Hmmm... not really.
On my Gentoo Linux (2.4.28-gentoo-r8):
it seems to timeout for connection but absolutely non-fatally -- Ctrl-Z
backgrounds the svn command, and then I can simply 'kill -9' it:
saulius@kolibris: codepuchino/ > svn co svn://codepuccino.com/
<Ctrl-Z pressed here>
[1]+ Stopped svn co svn://codepuccino.com/
saulius@kolibris: codepuchino/ > kill %1
[1]+ Stopped svn co svn://codepuccino.com/
saulius@kolibris: codepuchino/ > kill -9 %1
[1]+ Stopped svn co svn://codepuccino.com/
saulius@kolibris: codepuchino/ >
[1]+ Killed svn co svn://codepuccino.com/
saulius@kolibris: codepuchino/ >
No other applications are affected, everything functions and I can work as
usually while 'svn' timeouts.
If I wait for a while, I get timeout message:
saulius@kolibris: codepuchino/ > svn co svn://codepuccino.com/
svn: Can't connect to host 'codepuccino.com': Connection timed out
The same works on 2.6.11-gentoo-r8 kernel.
--
Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax: (+370-5)-210 40 05
mobilus: (+370-684)-49802, (+370-614)-36366
Re: Major bug in svn command line client
Posted by John Szakmeister <jo...@szakmeister.net>.
Theo Van Dinter wrote:
> On Tue, Jul 19, 2005 at 04:07:24PM -0400, Robert S. Sfeir wrote:
>
>>>Not a problem here. The attempted checkout *did* hang, but opening a
>>>new SSH connection and killing the process unlocked it just fine.
>>
>>Yup hence a problem don't you think? Opening a new ssh session to
>>kill svn?
>
>
> As I recall, this is a known bug in neon.
>
> For this issue, I usually hit ^Z, then "kill -9 %1".
>
This particular has nothing to do with Neon. Neon is only used on
http:// access. I believe Neon 0.25.0 should take care of your
particular problem though.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by Theo Van Dinter <fe...@kluge.net>.
On Tue, Jul 19, 2005 at 04:07:24PM -0400, Robert S. Sfeir wrote:
> >Not a problem here. The attempted checkout *did* hang, but opening a
> >new SSH connection and killing the process unlocked it just fine.
>
> Yup hence a problem don't you think? Opening a new ssh session to
> kill svn?
As I recall, this is a known bug in neon.
For this issue, I usually hit ^Z, then "kill -9 %1".
--
Randomly Generated Tagline:
When money talks there are few interruptions.
Re: Major bug in svn command line client
Posted by Saulius Grazulis <gr...@akl.lt>.
On Tuesday 19 July 2005 23:07, Robert S. Sfeir wrote:
> >> Watch the machine hang. On OSX I can no longer start any apps, and
> >> rebooting is not possible either I have to force a shutdown and
> >> restart.
> >>
> >> Can someone please triple confirm this?
> >
> > Not a problem here. The attempted checkout *did* hang, but opening a
> > new SSH connection and killing the process unlocked it just fine.
>
> Yup hence a problem don't you think? Opening a new ssh session to
> kill svn?
Thats a usual Unix stuff with long timeouts. If you don't want to have extra
ssh connection to kill a process, just wait 2-3 min for a process to timeout.
That OSX hangs completely is another story, this shouldn't be. But this is
then definitely a bug in OSX (no user process should be able to hang a
kernel, right? ;), not in subversion. And maybe its also just a long timeout?
--
Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax: (+370-5)-210 40 05
mobilus: (+370-684)-49802, (+370-614)-36366
Re: Major bug in svn command line client
Posted by Saulius Grazulis <gr...@akl.lt>.
On Wednesday 20 July 2005 14:46, Vincent Lefevre wrote:
> > Yup hence a problem don't you think? Opening a new ssh session to
> > kill svn?
>
> If Ctrl-C (SIGINT) doesn't work and you want something faster than
> Ctrl-Z + kill, then you may try Ctrl-\ (SIGQUIT).
Oh! Cool! I did not know this. Works fine ;).
> This generally
> works, but generates a core dump by default.
... which you could probably avoid by setting allowed size of core file to
zero:
ulimit -c 0
--
Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax: (+370-5)-210 40 05
mobilus: (+370-684)-49802, (+370-614)-36366
Re: Major bug in svn command line client
Posted by Vincent Lefevre <vi...@vinc17.org>.
On 2005-07-19 16:07:24 -0400, Robert S. Sfeir wrote:
> Yup hence a problem don't you think? Opening a new ssh session to
> kill svn?
If Ctrl-C (SIGINT) doesn't work and you want something faster than
Ctrl-Z + kill, then you may try Ctrl-\ (SIGQUIT). This generally
works, but generates a core dump by default.
--
Vincent Lefèvre <vi...@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by "Robert S. Sfeir" <yo...@gmail.com>.
On Jul 19, 2005, at 3:54 PM, Kris Deugau wrote:
> "Robert S. Sfeir" wrote:
>
>> This one bit me one too many times, but apparently we can now
>> reproduce this on OS X and Linux. Clients tested were 1.1.1, 1.1.4
>> and 1.2.0.
>>
>> If you have OS X or Linux try this (At your own risk)
>>
>> at the command line type:
>>
>> svn co svn://codepuccino.com/
>>
>> press enter
>>
>> press ctrl + c to kill it since it's not the right port.
>>
>> Watch the machine hang. On OSX I can no longer start any apps, and
>> rebooting is not possible either I have to force a shutdown and
>> restart.
>>
>> Can someone please triple confirm this?
>>
>
> Not a problem here. The attempted checkout *did* hang, but opening a
> new SSH connection and killing the process unlocked it just fine.
Yup hence a problem don't you think? Opening a new ssh session to
kill svn?
R
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by Kris Deugau <kd...@vianet.ca>.
"Robert S. Sfeir" wrote:
> This one bit me one too many times, but apparently we can now
> reproduce this on OS X and Linux. Clients tested were 1.1.1, 1.1.4
> and 1.2.0.
>
> If you have OS X or Linux try this (At your own risk)
>
> at the command line type:
>
> svn co svn://codepuccino.com/
>
> press enter
>
> press ctrl + c to kill it since it's not the right port.
>
> Watch the machine hang. On OSX I can no longer start any apps, and
> rebooting is not possible either I have to force a shutdown and
> restart.
>
> Can someone please triple confirm this?
Not a problem here. The attempted checkout *did* hang, but opening a
new SSH connection and killing the process unlocked it just fine.
Running Debian woody with Subversion installed from backports.org:
kdeugau@test0:~/test$ svn --version
svn, version 1.1.3 (r12730)
compiled Jan 22 2005, 21:00:23
-kgd
--
Get your mouse off of there! You don't know where that email has been!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by Patrick Burleson <pb...@gmail.com>.
On 7/19/05, John Szakmeister <jo...@szakmeister.net> wrote:
> Robert S. Sfeir wrote:
> > This one bit me one too many times, but apparently we can now reproduce
> > this on OS X and Linux. Clients tested were 1.1.1, 1.1.4 and 1.2.0.
> >
> > If you have OS X or Linux try this (At your own risk)
> >
> > at the command line type:
> >
> > svn co svn://codepuccino.com/
> >
> > press enter
> >
> > press ctrl + c to kill it since it's not the right port.
>
> What do you mean "it's not the right port?" Do you mean that you meant
> to type "http://codepuccino.com" instead?
>
It looks as if he's running svnserver on a non standard port, but
*something* is listening to the standard port. Telneting to
codepuccino.com 3690 shows that something picks up the connection, but
never sends any data. I'm guessing SVN is stuck waiting for data, but
for some reason has stopped responding to Ctrl-C.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Major bug in svn command line client
Posted by John Szakmeister <jo...@szakmeister.net>.
Robert S. Sfeir wrote:
> This one bit me one too many times, but apparently we can now reproduce
> this on OS X and Linux. Clients tested were 1.1.1, 1.1.4 and 1.2.0.
>
> If you have OS X or Linux try this (At your own risk)
>
> at the command line type:
>
> svn co svn://codepuccino.com/
>
> press enter
>
> press ctrl + c to kill it since it's not the right port.
What do you mean "it's not the right port?" Do you mean that you meant
to type "http://codepuccino.com" instead?
> Watch the machine hang. On OSX I can no longer start any apps, and
> rebooting is not possible either I have to force a shutdown and restart.
>
> Can someone please triple confirm this?
Can you provide more information? For instance, how did you launch
svnserve? What options did you pass it?
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org