Even with the latest Fossil, I'm continuing to have problems with reparent. I'm also continuing to fail to produce a repeatable test case or even a repository I can share without endangering my livelihood. I've been trying for a couple years now, ever since reparent was first introduced. One would think a problem would be more likely to show itself in a stress test than in casual use, but here it's the opposite. A real Heisenbug.
Today I resigned myself to the notion that I have to debug it on my own. I did find something, but I'm not sure it's even the issue I started out looking for, same as occurred recently for two issues with changing dates. I'm getting missing events in the database following rebuild or reconstruct, but the manifests and plinks and mlinks are all there. This results in holes in the timeline. I'm guessing the culprit is the test to only create the check-in event if there are no mlinks yet. Depending on artifact visitation order, this assumption might not work out too well. If the reparent tag is handled before the original check-in, will its event be created?
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
