Bzr error while commiting

[Ralph Douglass]

Nope, no sort of network interruption that I was aware of.  It's on the 
local network too.

bzr help break-lock says that I can find out what locks are open via bzr 
info, but running that gives no information on locks.

I made sure no processes where running any more related to bzr on the 
remote server, broke lock, and then tried to commit again.  It gave me 
the same error again.  Maybe an upgrade to .90 will fix this for me.

John Arbash Meinel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ralph Douglass wrote:
>   
>> I got this while commiting.  I didn't see anything in the man page or
>> bzr help commit about forced unlocking.  Any thoughts on how to recover?
>>
>> [====================================                        ] Uploading
>> data to master branch - Stage 3/5Traceback (most recent call last):
>>  File "/usr/bin/bzr", line 116, in ?
>>    sys.stdout.flush()
>> ValueError: I/O operation on closed file
>> bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium
>> '<bzrlib.smart.medium.SmartSSHClientMedium object at 0x2ac24ef4ed50>'
>> has reached its concurrent request limit. Be sure to finish_writing and
>> finish_reading on the currently open request.
>>
>>     
>
> This sounds like you disconnected in the middle of a commit. Did your network
> connection go down, or some other sort of interruption.
>
> We really shouldn't be giving a traceback (it should just be a ConnectionError).
>
> Oh, and 'bzr help break-lock' if you need to unlock because you disconnected in
> the middle.
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG2CZKJdeBCYSNAAMRAi/vAKDOX4ENC/pnl9s9/0TOhVftt0RDrQCgjlA8
> sJNxG2IRMQnvtyuFkQmQits=
> =iaLb
> -----END PGP SIGNATURE-----
>
>
>