On Tue, Apr 22, 2014 at 9:30 PM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Thus said Stephan Beal on Tue, 22 Apr 2014 18:07:08 +0200:
>
> > Just to confirm that: this has come up several times before in the
> > past year and, so far, has remained unexplained. We're not sure what
> > causes it or how to reproduce it. (At least i don't remember seeing
> > any commits/posts which explain/fix it.)
>
> The only time I've ever seen it *not* update to the latest commit in a
> remote repository is when a sync has failed. For example:
>
> $ ../fossil ci -m bottom
> Autosync: ssh://remote//tmp/test.fossil?fossil=/tmp/fossil
> Round-trips: 2 Artifacts sent: 0 received: 18
> Pull finished with 1063 bytes sent, 298025 bytes received
> New_Version: 18febd6eb320521d5b730d237381d001b562496e
> Autosync: ssh://remote//tmp/test.fossil?fossil=/tmp/fossil
> Round-trips: 1 Artifacts sent: 2 received: 0
> Error: Database error: database is locked: {INSERT INTO rcvfrom(uid,
> mtime, nonce, ipaddr)VALUES(1, julianday('now'), NULL, '192.168.1.5')}
> Round-trips: 1 Artifacts sent: 2 received: 0
> Sync finished with 1586 bytes sent, 290 bytes received
> Autosync failed
> $ ../fossil up
> Autosync: ssh://remote//tmp/test.fossil?fossil=/tmp/fossil
> Round-trips: 3 Artifacts sent: 0 received: 84
> Pull finished with 3012 bytes sent, 1355913 bytes received
>
> -------------------------------------------------------------------------------
> checkout: 18febd6eb320521d5b730d237381d001b562496e 2014-04-23 04:18:45
> UTC
> tags: trunk
> comment: bottom (user: amb)
> changes: None. Already up-to-date
>
> But I know that 18fe is not the tip of trunk. If I manually tell it to
> update to 5f75 it will update. Also, because the sync failed, I don't
> see my commit on the remote repository yet. Once I do a sync it shows up
> though, and after I sync I actually see that a fork has occurred.
>
> Is this the same issue that others are seeing? Hard to say, but it's the
> only time I've observed any kind of failure to update.
>
I haven't seen this problem in quite a while but what we saw was the sync
had occurred and yet we couldn't update to the tip. I had suspected this
issue was solved, perhaps indirectly or by other development. It is rare
enough and easy enough to work around that other than reporting it I
haven't worried about it. Unfortunately in every case it happened the repo
in question contained data that could not be shared so I couldn't provide a
testcase.
This has happened enough that I'm sure it was a real issue but it has been
long enough since anyone reported it to me that I'd assumed it was fixed.
> Andy
> --
> TAI64 timestamp: 4000000053574221
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
