Timeout when writing long commit messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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:
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
Changed in bzr: | |
status: | New → Confirmed |
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.