On Wed, Apr 16, 2014 at 3:40 PM, Rich Neswold <[email protected]> wrote: > It would be even nicer if it didn't throw away partial "pull" data on > a DB timeout: > > I'm trying to pull the latest NetBSD changes (to pull in the > Heartbleed fixes) and my session keeps failing with the "fudge time" > error. Unfortunately, this means all the data it transferred > (sometimes over 1GB!) gets rolled back and I have to try again later. > > It would be nice if fossil would break the "pull" into smaller > transactions which contain valid timeline commits so, if there's a > database timeout, the next time I try to "pull" it can continue where > it left off.
I may be confused and I'm definitely ignorant of fossil internals. The first few times that my "pull"s failed, there was no obvious change to the timeline so I assumed none of the data was being saved. After the last timeout, however, there were some new entries from the NetBSD project. So maybe new pulls start were the previous left off after all. (The heartbleed bug probably caused many changes to several NetBSD branches, so there are probably many more entries to pull than normal.) I'll hit Mr. Sonnenberger's server a few more time throughout the day and see if I can eventually complete a pull. -- Rich _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
