monotone - Bugs: bug #28991, montone sync failure
You are not allowed to post comments on this tracker with your current authentication level.
bug #28991: montone sync failure
Submitter: | Neil <fnm> | ||
Submitted: | Tue 23 Feb 2010 03:04:43 PM UTC | ||
Category: | networking | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | Fixed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | ||
mtn version --full: | monotone 0.46 (base revision: unknown)
|
Jump to the original submission
Mon 15 Mar 2010 04:44:38 PM UTC, comment #6: |
Neil <fnm> |
Sun 14 Mar 2010 11:46:49 PM UTC, comment #5: 0.47 has just been released, which includes a fix for this |
Timothy Brownawell <tbrownaw> |
Thu 25 Feb 2010 03:57:38 PM UTC, comment #4: I think I'll stick with 0.45 for now and try 0.47 when it is released.
|
Neil <fnm> |
Thu 25 Feb 2010 01:28:20 PM UTC, comment #3: Prior to 0.46, the server would sometimes block waiting for I/O. We fixed this, but introduced another bug due to our networking library not liking non-blocking sockets. This would result in each side thinking the other had disconnected with no reason, when a sufficiently large file was transferred.
|
Timothy Brownawell <tbrownaw> |
Thu 25 Feb 2010 10:17:03 AM UTC, comment #2: O.K. --debug logs coming soon.
|
Neil <fnm> |
Thu 25 Feb 2010 01:42:05 AM UTC, comment #1: It looks like the server is getting confused and dropping the connection. Does it (the server) produce any output? If you run it with --debug, what does it output (this will produce a lot of output, so probably do this on a "retry" pull)?
|
Timothy Brownawell <tbrownaw> |
Tue 23 Feb 2010 03:04:43 PM UTC, original submission:
Since upgrading my monotone server from 0.45 to 0.46 I've been unable to clone a database. I.e:
|
Neil <fnm> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-03-14 | tbrownaw | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
2010-02-25 | fnm | Attached File | - | Added mtn_bug_28991_logs1.tar.bz2, #19793 |
Powered by Savane 3.13-4b48.
Corresponding source code
I've just installed version 0.47 and pulled my entire database without any trouble. Looks like the problem is indeed fixed.