Break-lock: Bzr doesn't accept my keystrokes to allow it to continue

Bug #217134 reported by Craig Hewetson on 2008-04-14
4
Affects Status Importance Assigned to Milestone
Bazaar
High
Unassigned

Bug Description

I've been trying to break a lock with the following command:
bzr break-lock bzr+ssh://<email address hidden>/~craighewetson/bzr-eclipse/craig_dev
it then asked for my passphrase and it then gave the following:

Break lock bzr+ssh://<email address hidden>/%7Ecraighewetson/bzr-eclipse/craig_dev/.bzr/repository/lock
held by <my email address> on host craig [process #2292]
locked 10 hours, 6 minutes ago? [y/n]:

At this point it does not echo any of my key strokes and if I type in y and strike the enter key is does nothing and just has the cursor blinking on the same line as it was before i typed in.

Interestingly, if i type 2 character straight after each other i.e 'c' 'y' then it echos/displays the 'y' char only.

so by using this hack I type in c and the y (but in quick succession) and then I typing in 'c' and 'enter' (in quick succession). And the cursor will be on the next line with the following displayed:

Break lock bzr+ssh://<email address hidden>/%7Ecraighewetson/bzr-eclipse/craig_dev/.bzr/repository/lock
held by <my email address> on host craig [process #2292]
locked 10 hours, 6 minutes ago? [y/n]:y

Even with this it still seems "stuck".

This is starting to be a real problem. It won't allow me to break the lock that I inadvertently created because of other problems I was having.
Is there any other way of breaking this lock. (maybe having some timeout mechanism, that only counts up once when it does not detect any activity etc). Because I think the only way i can start pushing my changes to this (empty) branch would be to create a new one etc.

Craig Hewetson (craighewetson) wrote :

Another effect that this has it that my console (cmd terminal) does not respond to right clicks and ctrl-C etc
When i type ctrl-z it just repeats the output.

I hope this is enough info.

Alexander Belchenko (bialix) wrote :

are you working on Cygwin?

Craig Hewetson (craighewetson) wrote :

Nope ... I'm just using windows default command prompt. (Terrible thing)

I just don't have the option to use Ubuntu on this particular machine.

Craig Hewetson пишет:
> Nope ... I'm just using windows default command prompt. (Terrible thing)

Try FAR instead.

I'm not sure where is your problem lies. As I could see you're using
python-based version of bzr, right? I don't ask you why you're not
using standalone bzr.exe, but just for testing: could you try
to uninstall python-based and temporary install standalone version
and try again. Does bzr.exe also have this problems?

Craig Hewetson (craighewetson) wrote :

I don't think i will get the time to go through the motions etc. Need to make/build it etc (and i might have to install this and that etc etc).

Besides isn't the bzr.exe based on the python-based one? If this is true, then by fixing this bug for the python-based one will automatically fix it for the bzr.exe (if the bug is in the exe).

But if this is very important to finding a solution, i will try and go through the motions of making the exe and installing it. If there is a pre-built exe with the same version of bzr etc then
this will make it even easier to test.

Vincent Ladeuil (vila) on 2008-09-05
Changed in bzr:
status: New → Confirmed
John A Meinel (jameinel) wrote :

I can't reproduce this here. Is it possible it is the ssh client you are using (plink, paramiko?)

I'll admit to running "from source", but using plain 'cmd.exe' and a simple bzr.bat script, I'm able to type 'y<enter>' without any problems.

Changed in bzr:
importance: Undecided → High
status: Confirmed → Incomplete
Scott Armitage (scott-armitage) wrote :

I have encountered this problem as well, using both cmd.exe and Windows PowerShell.

Symptoms:
-----------------
When trying to break a Bazaar lock (specifically on a branch hosted by Launchpad), bzr.exe hangs on prompt and does not accept single keystrokes. Double keystrokes (in very quick succession) accept the second keystroke only. Holding down a particular key will result in entering that keystroke repeatedly, though I suspect the first instance is being ignored (as with the other scenarios). Ctrl-C is also ignored, meaning Task Manager -> End Task bzr.exe.

Version information:
-----------------------------
Bazaar (bzr) 1.17
  Python interpreter: C:\Program Files\Bazaar\python25.dll 2.5.4
  Python standard library: C:\Program Files\Bazaar\lib\library.zip
  bzrlib: C:\Program Files\Bazaar\lib\library.zip\bzrlib
  Bazaar configuration: C:\Documents and Settings\sarmitage\Application Data\bazaar\2.0
  Bazaar log file: C:\Documents and Settings\sarmitage\My Documents\.bzr.log

Bazaar log entry:
-------------------------
Thu 2009-08-06 09:29:13 -0400
0.078 bzr arguments: [u'break-lock', u'lp:pype']
0.078 looking for plugins in C:/Documents and Settings/sarmitage/Application Data/bazaar/2.0/plugins
0.078 looking for plugins in C:/Program Files/Bazaar/plugins
0.172 encoding stdout as sys.stdout encoding 'cp437'
1.141 bzr-svn: using Subversion 1.5.4 ()
2.750 opening SVN RA connection to 'bzr+ssh://bazaar.launchpad.net/~scott-armitage/pype/trunk'
2.907 ssh implementation is OpenSSH
7.641 encoding stdout as sys.stdout encoding 'cp437'

Command output:
--------------------------
Break lock bzr+ssh://bazaar.launchpad.net/~scott-armitage/pype/trunk/.bzr/branch/lock
held by <email address hidden> on host crowberry [process #31730]
locked 45 hours, 58 minutes ago? [y/n]:

Scott Armitage (scott-armitage) wrote :

FYI, I was able to work around this using pipes to force a "y\n" into bzr break-lock:

echo y | bzr break-lock lp:pype

Launchpad Janitor (janitor) wrote :

[Expired for Bazaar because there has been no activity for 60 days.]

Changed in bzr:
status: Incomplete → Expired
Jelmer Vernooij (jelmer) on 2011-03-19
Changed in bzr:
status: Expired → Confirmed
Jelmer Vernooij (jelmer) on 2017-11-08
tags: added: check-for-breezy
Jelmer Vernooij (jelmer) on 2017-11-11
tags: removed: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers