Maybe bite off one smallish easy case and mail it out to try and force someone to think about it?
> On Jul 15, 2020, at 16:50, Rodrigo Damazio <rdama...@google.com> wrote: > > Thanks Augie. Me too. > If nobody has thoughts I'll start sending (large, invasive) code changes soon > :) > > > On Wed, Jul 15, 2020 at 9:20 AM Augie Fackler <r...@durin42.com > <mailto:r...@durin42.com>> wrote: > I think this makes sense, but I'd love to hear feedback from non-Google > people... > >> On Jun 12, 2020, at 20:10, Rodrigo Damazio via Mercurial-devel >> <mercurial-devel@mercurial-scm.org >> <mailto:mercurial-devel@mercurial-scm.org>> wrote: >> >> Hi everyone. >> >> Any comments on this early proposal are most welcome: >> https://www.mercurial-scm.org/wiki/ErrorCategoriesPlan >> <https://www.mercurial-scm.org/wiki/ErrorCategoriesPlan> >> >> Our motivation is to measure the user experience our users are actually >> getting, and have realtime pager alerts if e.g. a new client or server >> release causes a big change, but not count or alert on errors that are "not >> our fault", such as bad user input. >> For instance, we have up to 70% error rates on weekends because some people >> leave something like "hg status" or "hg log" running in a loop on a >> terminal, and their credentials expire - those should not be counted at all. >> Even in the middle of workdays, our running error rate is way more than it >> "should" be, because we currently measure all non-zero status codes. >> >> Thanks >> Rodrigo >> >> _______________________________________________ >> Mercurial-devel mailing list >> Mercurial-devel@mercurial-scm.org <mailto:Mercurial-devel@mercurial-scm.org> >> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel >> <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel> >
_______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
