Re: [fossil-users] Autosync retry?
Thus said Martin Gagnon on Fri, 30 May 2014 05:55:58 -0400: Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. The actually do serve different purposes. dont-push=1 prevents *all* pushes from happening. autosync=pull-only only prevents autosync from doing a push, manual push still works. Andy -- TAI64 timestamp: 4000538f88c0 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Le 29 mai 2014 16:10, Stephan Beal sgb...@googlemail.com a écrit : Wasn't even aware of pull-only until earlier today. snip Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
On Fri, May 30, 2014 at 11:55 AM, Martin Gagnon eme...@gmail.com wrote: Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. LOL - wasn't aware of dont-push, either ;) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
On Fri, May 30, 2014 at 5:55 AM, Martin Gagnon eme...@gmail.com wrote: Le 29 mai 2014 16:10, Stephan Beal sgb...@googlemail.com a écrit : Wasn't even aware of pull-only until earlier today. snip Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. As I recall, the 2 options have slightly different affects. pull-only only affects auto sync, while dont-push affects both manual and auto sync. A manual push will, of course, still push. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Thus said Ron Wilson on Fri, 30 May 2014 09:42:44 -0400: As I recall, the 2 options have slightly different affects. pull-only only affects auto sync, while dont-push affects both manual and auto sync. A manual push will, of course, still push. ``pull-only'' pertains only to the autosync code (used by checkin and update), however, ``dont-push'' also affects autosync. It does appear, however, that ``push-only'' also affects manual pushes, so they seem to have different purposes: http://www.fossil-scm.org/index.html/artifact/912d6a207a3e070b3b2c1c46d2395ff3e4ec76c2?ln=203,205 It also affect any client_sync operation in general: http://www.fossil-scm.org/index.html/artifact/37f2afbbd186bf5cef90c57b7fa1acd7097977cd?ln=1418 Andy -- TAI64 timestamp: 400053889b85 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Autosync retry?
Hello, I introduced some code on the autosync-tries branch that causes autosync to retry if it fails, up to a maximum of 3 tries. 1) Should autosync retry? 2) Should the number of tries be configurable? I would like to either merge or abandon, but would like some additional feedback first. Here are the current changes: http://www.fossil-scm.org/index.html/vdiff?from=8a5f192b40401748to=9f33dbae40a02321sbs=1 Thanks, Andy -- TAI64 timestamp: 40005387487e ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
On Thu, May 29, 2014 at 4:53 PM, Richard Hipp d...@sqlite.org wrote: On Thu, May 29, 2014 at 10:46 AM, Andy Bradford amb-fos...@bradfords.org wrote: 1) Should autosync retry? In my experience, autosync only fails when WIFI is down (or turned off). Retries won't help that. It just takes longer to finish. Maybe instead of autosync being a toggle... autosync 0 == off 1 == current behaviour 2+ == retry up to N-1 times or some such? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
On Thu, May 29, 2014 at 10:46 AM, Andy Bradford amb-fos...@bradfords.org wrote: Hello, I introduced some code on the autosync-tries branch that causes autosync to retry if it fails, up to a maximum of 3 tries. 1) Should autosync retry? In my experience, autosync only fails when WIFI is down (or turned off). Retries won't help that. It just takes longer to finish. 2) Should the number of tries be configurable? I would like to either merge or abandon, but would like some additional feedback first. Here are the current changes: http://www.fossil-scm.org/index.html/vdiff?from=8a5f192b40401748to=9f33dbae40a02321sbs=1 Thanks, Andy -- TAI64 timestamp: 40005387487e ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
I'd rather autosync remained a toggle (indicating whether work is local or not). A separate setting for number of retries seems reasonable. On Thu, May 29, 2014 at 3:56 PM, Stephan Beal sgb...@googlemail.com wrote: On Thu, May 29, 2014 at 4:53 PM, Richard Hipp d...@sqlite.org wrote: On Thu, May 29, 2014 at 10:46 AM, Andy Bradford amb-fos...@bradfords.org wrote: 1) Should autosync retry? In my experience, autosync only fails when WIFI is down (or turned off). Retries won't help that. It just takes longer to finish. Maybe instead of autosync being a toggle... autosync 0 == off 1 == current behaviour 2+ == retry up to N-1 times or some such? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Thus said Richard Hipp on Thu, 29 May 2014 10:53:57 -0400: In my experience, autosync only fails when WIFI is down (or turned off). Retries won't help that. It just takes longer to finish. I agree that for network related failures, retry won't help. Others have reported non-network related failures (primarily due to locking or other similar problems). Perhaps if we make the default to be 1 sync but then add a settting that governs the number of attempts when it fails? Thanks, Andy -- TAI64 timestamp: 400053875485 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Retry on autosync would be a big help in my environment. Autosync failures due to overlapping access are a regular and annoying occurrence. I like Stephan's approach of 0, 1, N for off, on, multi-try On Thu, May 29, 2014 at 8:49 AM, Andy Bradford amb-fos...@bradfords.orgwrote: Thus said Marc Simpson on Thu, 29 May 2014 16:35:50 +0100: I'd rather autosync remained a toggle (indicating whether work is local or not). A separate setting for number of retries seems reasonable. Well, strictly speaking, autosync isn't a toggle, it can also be set to ``pull-only'' :-) But I am of the opinion that autosync-tries should be a separate setting. Andy -- TAI64 timestamp: 400053875710 ___ 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
Re: [fossil-users] Autosync retry?
On Thu, May 29, 2014 at 6:00 PM, Matt Welland estifo...@gmail.com wrote: Retry on autosync would be a big help in my environment. Autosync failures due to overlapping access are a regular and annoying occurrence. I like Stephan's approach of 0, 1, N for off, on, multi-try That could also (more simply, i think) be interpreted as: 0 == off 1+ == number of times to try -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Thus said Stephan Beal on Thu, 29 May 2014 18:06:49 +0200: That could also (more simply, i think) be interpreted as: 0 == off 1+ == number of times to try I'm a bit confused, however, in how 0 and 1 should be interpreted... Given that Fossil currently does 1 autosync attempt: Does 0 mean no autosync attempts (seem that's the purpose of the current autosync setting)? Or does it mean the current behavior of 1 attempt? Furthermore, does 1 mean 1 more than the current behavior of 1 autosync attempt? Thanks, Andy -- TAI64 timestamp: 400053878cb7 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
0 means no autosync, 1 means one attempt (same as now), 2+ means retry N times. But because there really is no difference between try and retry, 1+ is the same logic: For(i=0; i N; ++i) attempt to sync, break on success. (sent from a mobile device - please excuse brevity, typos, and top-posting) - stephan beal http://wanderinghorse.net On May 29, 2014 9:38 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Stephan Beal on Thu, 29 May 2014 18:06:49 +0200: That could also (more simply, i think) be interpreted as: 0 == off 1+ == number of times to try I'm a bit confused, however, in how 0 and 1 should be interpreted... Given that Fossil currently does 1 autosync attempt: Does 0 mean no autosync attempts (seem that's the purpose of the current autosync setting)? Or does it mean the current behavior of 1 attempt? Furthermore, does 1 mean 1 more than the current behavior of 1 autosync attempt? Thanks, Andy -- TAI64 timestamp: 400053878cb7 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Thus said Stephan Beal on Thu, 29 May 2014 21:44:12 +0200: 0 means no autosync, 1 means one attempt (same as now), 2+ means retry N times. But because there really is no difference between try and retry, 1+ is the same logic: I assume we're talking about a different setting than the current autosync setting because I might want to have autosync try multiple times *and* have it set to pull-only. Given this, if autosync is on (or pull-only) and autosync-tries is 0, does that mean autosync does not happen? Effectively making 2 ways to express the desire to have autosync off. Or should autosync-tries be ignored if 0 (e.g. just use the current behavior)? Thanks, Andy -- TAI64 timestamp: 400053878fe0 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Wasn't even aware of pull-only until earlier today. i am completely ambivalent on the topic - never had any problems with autosync - this was just what came to mind when you posted. Seemed easier than adding a new option, but was not aware of the pull-only feature (so a second option might be simpler). (sent from a mobile device - please excuse brevity, typos, and top-posting) - stephan beal http://wanderinghorse.net On May 29, 2014 9:51 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Stephan Beal on Thu, 29 May 2014 21:44:12 +0200: 0 means no autosync, 1 means one attempt (same as now), 2+ means retry N times. But because there really is no difference between try and retry, 1+ is the same logic: I assume we're talking about a different setting than the current autosync setting because I might want to have autosync try multiple times *and* have it set to pull-only. Given this, if autosync is on (or pull-only) and autosync-tries is 0, does that mean autosync does not happen? Effectively making 2 ways to express the desire to have autosync off. Or should autosync-tries be ignored if 0 (e.g. just use the current behavior)? Thanks, Andy -- TAI64 timestamp: 400053878fe0 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
On Thu, May 29, 2014 at 11:38 AM, Andy Bradford amb-fos...@bradfords.org wrote: I agree that for network related failures, retry won't help. Others have reported non-network related failures (primarily due to locking or other similar problems). Intermittent network failures can be a problem.So, when I'm not at the office, I usually turn off auto sync and run a sync script that tries the sync 5 times, wating a minute between tries. This usually works, but is rather slow. (Besides the office, my work involves hands on time in various labs and manufacturing facilities that are electrically noisy. (The machinery is connected to an ethernet that has no connection to even the company intranet, let alone the internet)) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
Thus said Stephan Beal on Thu, 29 May 2014 22:10:24 +0200: Wasn't even aware of pull-only until earlier today. i am completely ambivalent on the topic - never had any problems with autosync - this was just what came to mind when you posted. Seemed easier than adding a new option, but was not aware of the pull-only feature (so a second option might be simpler). Actually, I thought it was a great idea except that it conflicted with pull-only. I agree that it will be simpler as a separate setting: http://www.fossil-scm.org/index.html/info/7653ab63420e4ab4ca6372a53de9314a18e1b946 It will default to 1 so it retains the same behavior as Fossil without the setting. Setting it greater than 1 allows those who want Fossil to try harder to get more tries. Autosync (on/off) itself is still governed by the autosync setting. Andy -- TAI64 timestamp: 40005387fc6d ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Autosync retry?
I was going to +1 sbeals idea, but the pull-only autosync note came up, and now I think I may not know all there is about autosync. Thanks for keeping it interesting, folks. On May 29, 2014 8:34 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Stephan Beal on Thu, 29 May 2014 22:10:24 +0200: Wasn't even aware of pull-only until earlier today. i am completely ambivalent on the topic - never had any problems with autosync - this was just what came to mind when you posted. Seemed easier than adding a new option, but was not aware of the pull-only feature (so a second option might be simpler). Actually, I thought it was a great idea except that it conflicted with pull-only. I agree that it will be simpler as a separate setting: http://www.fossil-scm.org/index.html/info/7653ab63420e4ab4ca6372a53de9314a18e1b946 It will default to 1 so it retains the same behavior as Fossil without the setting. Setting it greater than 1 allows those who want Fossil to try harder to get more tries. Autosync (on/off) itself is still governed by the autosync setting. Andy -- TAI64 timestamp: 40005387fc6d ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
