Fossil: View Ticket

2010-10-08
18:17		• Ticket [cf67fa9343] Fossil crashes when committing status still Closed with 1 other change ... (artifact: 65e231e516 user: anonymous)
18:05		• Closed ticket [cf67fa9343]. ... (artifact: 0b253b7849 user: anonymous)
16:03		• Ticket [cf67fa9343]: 1 change ... (artifact: d593f09961 user: wolfgang)
15:46		• Ticket [cf67fa9343]: 2 changes ... (artifact: 46c1c61481 user: anonymous)
14:53		• New ticket [cf67fa9343]. ... (artifact: de266a2a93 user: anonymous)

Ticket Hash:	cf67fa9343e145dee3d2600da7184eaffa8064ce
Title:	Fossil crashes when committing
Status:	Closed	Type:	Incident
Severity:	Important	Priority:
Subsystem:		Resolution:	Works_As_Designed
Last Modified:	2010-10-08 18:17:27 15.49 years ago	Created:	2010-10-08 14:53:18 15.49 years ago
Version Found In:	[cfbbad3d48] 2010-10-08 10:59:53 UTC

Description:

I wanted to see if Fossil would be able to pull changesets/revisions from one repo to another (like Hg does). However, during testing, it kept crashing when I tried to commit.

Here are the steps I did:

** The following commands all occur within the "test1" directory
$ fossil new tr1.fsl
$ fossil open tr1.fsl
$ fossil add file1.txt
$ fossil ci -m "Initial commit"
...Edited file1.txt...
$ fossil ci -m "Removed some lines"
$ cd ../test2

** The following commands all occur within the "test2" directory
$ fossil clone http://localhost:8080/ tr2.fsl -> success
$ fossil open tr2.fsl -> success
..Edited file 1.txt...
$ fossil ci -m "Added lines at the end"

I am using a Windows 7 box for this.

anonymous added on 2010-10-08 15:46:27:
I forgot to mention: tr2.fsl is a clone of tr1.fsl. Running sqlite3 "pragma integrity_check" on both test repos returns ok.

wolfgang added on 2010-10-08 16:03:41:
i could reproduce the error on Win XP SP2

The error does not appear, if autosync is switched off.

anonymous added on 2010-10-08 18:05:50:
Ah, yes. New repos do have that option enabled by default.

I just tried it now and it works. Thanks!

anonymous added on 2010-10-08 18:17:27:
Can I at least request for an error message to be shown instead of Fossil crashing? That way, it could point users to which they need to change.