Re: [fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).
On 08/09/11 15:14, Martin S. Weber wrote: I stumbled over this while I had a network outage... ...so what's the new workflow now that I as anonymous cannot create a ticket to capture that problem. Will I get an ACK on this list? Will a ticket be silently created by someone? Will there be a followup on this list once a problem-solving commit (or the decision it's not a bug, it's a feature) happened? This ought to be documented, IMO... Regards, -Martin ___ 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] Bug: errant operations don't cause exit(EXIT_FAILURE).
On Thu, Aug 11, 2011 at 5:25 PM, Martin S. Weber martin.we...@nist.govwrote: On 08/09/11 15:14, Martin S. Weber wrote: I stumbled over this while I had a network outage... ...so what's the new workflow now that I as anonymous cannot create a ticket to capture that problem. Will I get an ACK on this list? Will a ticket be silently created by someone? Will there be a followup on this list once a problem-solving commit (or the decision it's not a bug, it's a feature) happened? This ought to be documented, IMO... There are 47 people on this list who have the appropriate credentials to write a ticket and/or make changes to the code. All you have to do is convince 1 out of those 47 people that the problem is worth their time and effort. Or, failing that, you can fill out and send in a Copyright Release ( http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) and then you can become the 48th person with the credentials to write tickets and otherwise make changes, and then take care of the problem yourself. Yes, this all ought to be documented. Once again, all you have to do is convince somebody that doing so is worth their time and effort. Or you can send in a CLA and get the credentials to do it yourself. Regards, -Martin ___ 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] Bug: errant operations don't cause exit(EXIT_FAILURE).
On 08/11/11 17:39, Richard Hipp wrote: There are 47 people on this list who have the appropriate credentials to write a ticket and/or make changes to the code. All you have to do is convince 1 out of those 47 people that the problem is worth their time and effort. Or, failing that, you can fill out and send in a Copyright Release (http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) and then you can become the 48th person with the credentials to write tickets and otherwise make changes, and then take care of the problem yourself. Yes, this all ought to be documented. Once again, all you have to do is convince somebody that doing so is worth their time and effort. Or you can send in a CLA and get the credentials to do it yourself. Alright. I'll read the CLA carefully, try to become #48, take care of the problem myself if it hasn't been until then, and go ahead and document the procedure. Thanks, -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).
I stumbled over this while I had a network outage... $ until fossil configuration pull all fossil sync ; do echo; echo; date; echo; echo; sleep 5 ; done Bytes Cards Artifacts Deltas Sent: 58 1 0 0 fossil: cannot connect to host server:port Total network traffic: 0 bytes sent, 0 bytes received Server:http://user@server:port/repo Bytes Cards Artifacts Deltas Sent:3545 75 0 0 fossil: cannot connect to host server:port Total network traffic: 0 bytes sent, 0 bytes received Or in other words: $ fossil sync Server:http://user@server:port/repo Bytes Cards Artifacts Deltas Sent:3545 75 0 0 waiting for server...fossil: cannot connect to host server:port Total network traffic: 0 bytes sent, 0 bytes received $ echo $? 0 Imho it should have exit status != 0 in the case where the network communication failed due to an error. $ fossil version This is fossil version 1.18 [df9da91ba8] 2011-07-13 23:03:41 UTC Regards, -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
