monotone - Bugs: bug #7894, fix minor race conditions in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #7894: fix minor race conditions in working copy rewriting
Submitter: | graydon hoare <graydon> | ||
Submitted: | Tue 24 Feb 2004 08:50:11 PM UTC | ||
Category: | working copy | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: |
|
Thu 17 Feb 2005 08:17:33 AM UTC, comment #2: |
Nathaniel Smith <njs> |
Mon 14 Feb 2005 08:44:48 AM UTC, comment #1: Perhaps I'm thinking too simply here, but what's wrong with keeping a lock in the MT/ directory and refusing to run monotone in the directory if it's held? |
Jeremy Fincher <jemfinch> |
Tue 24 Feb 2004 08:50:11 PM UTC, original submission:
it is possible that if you run two copies of monotone concurrently or abort a run part way through an update or checkout, the working copy may be left in an inconsistent state relative to its manifest. no harm done to database, and the gap is already quite small and unlikely to be a problem; also unclear whether it's possible to solve perfectly. |
graydon hoare <graydon> |
No files currently attached
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.
Powered by Savane 3.13-cf05.
Corresponding source code
See tests/t_undo_update.at for a description of a feature that would be very nice anyway, and would perhaps make this problem reasonably easy to solve Correctly.