Timeout when writing long commit messages

[ian marcinkowski]

This is in response to a question opened by another user, but it is a common problem I face that has resulted in writing terrible commit messages, afraid of the dreaded 300 second limit to writing a commit message.

Bzr version: 2.6b2

Description of problem:
When writing a commit message for a bound branch using `bzr commit` the connection to my code repository times out after 300 seconds.

This causes the commit message I have carefully typed to be piped to /dev/null and I am forced to write it again in our ticketing system because it doesn't care how long I think about the best way to describe my changes. The branch is now locked, so I have to break the lock using bzr break-lock.

I usually have an active SSH connection to my code repository separate from the connection created by BZR, so I don't think this has anything to do with my network settings.

My setup:
- Changes on local dev machine > SSH > Code repo
- branch_location = bzr+ssh://code.example.com

Steps to reproduce:
1) Make some changes
2) bzr commit
3) Write commit message in favourite text editor
4) Take longer than 300 seconds
5) :wq
6) GRRR ARG

[Andrew Johnson (anj)]

If the timeout can't be removed, Bazaar should at least print out my carefully crafted commit message so I don't have to write it again from scratch, or save it to a local file from where it can pick it up again later. Another possible solution might be to prompt the user for the commit message *before* contacting the repository server, but that might cause similar annoyances if the commit has to be rejected for whatever reason.

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-02-01 23:37, Andrew Johnson wrote:
> If the timeout can't be removed, Bazaar should at least print out
> my carefully crafted commit message so I don't have to write it
> again from scratch, or save it to a local file from where it can
> pick it up again later. Another possible solution might be to
> prompt the user for the commit message *before* contacting the
> repository server, but that might cause similar annoyances if the
> commit has to be rejected for whatever reason.
>

New versions of bzr will retry the connection and the commit should
succeed. This should be fixed in bzr 2.5.0+

 status: fixreleased

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEPbhMACgkQJdeBCYSNAAPgfwCfXmnfkNRVVtY6VTKCGmdJFAr4
sLIAoJtiW1CTM4ib5u78Ts76DSvlodok
=nrRB
-----END PGP SIGNATURE-----

[Yves Baumes (ybaumes)]

I am using bzr v2.5.1:
$ bzr --version
Bazaar (bzr) 2.5.1
  Python interpreter: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python 2.7.3
  Python standard library: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
  Platform: Darwin-10.8.0-i386-64bit
  bzrlib: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/bzrlib
  Bazaar configuration: /Users/keugaerg/.bazaar
  Bazaar log file: /Users/keugaerg/.bzr.log

And I've got the issue after a while when trying to get branch the emacs trunk. As in `bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk trunk'.

It takes a long moment and then I have that issue. Does anyone have the same kind of issue?

[Estuda Maharyo Basuki (s2d4theworld)]

I experienced this problem with colo-fetch, after doing it for hours, it was killed with a message like "Connection Timeout: disconnecting client after 300.0 seconds" and "Killed" in the next line.