[PATCH] traceback: allow disabling the third party extensions blaming

Kevin Bullock kbullock+mercurial at ringworld.org
Tue Sep 22 10:09:39 CDT 2015


> On Sep 22, 2015, at 08:49, Augie Fackler <raf at durin42.com> wrote:
> 
> On Thu, Sep 17, 2015 at 02:43:56PM -0700, Sean Farley wrote:
>> 
>> Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:
>>> 
>>> I like the idea of having a different bugs report flow for big
>>> deployment that have there own support layer. We still need to do
>>> something about the user confusion and attempt to debug by disabling a
>>> long list of extensions one by one.
>> 
>> I have never once gotten anything useful out of the "possibly-broken"
>> list because it has never been correct. In fact, I've trained myself to
>> completely ignore it. I'm positive end-users are baffled as well. I like
>> Pierre-Yves' direction but don't know how to proceed.
> 
> Perhaps we should list *all* the extensions with outdated or missing
> testedwith lines, rather than merely picking one.

I think that would increase the utility of the message. When I go about debugging a traceback like this, I start by disabling all the things that I know are 3rd-party extensions; but I almost certainly have more off-the-cuff knowledge of which ones those are than the average user who installs a few 3rd-party extensions.

Seeing a list of all the 3rd-party extensions that haven't set testedwith would let me start by disabling all of those (which will probably also be a smaller set than "all 3rd-party extensions I've installed").

As far as the rest of this thread goes, I'm with Matt and Augie. Easing our volunteer support burden and encouraging due diligence on the part of 3rd-party extension authors continue to be valuable. I'm keen to find other fixes than disabling this message in precisely the environment where it could be most useful.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock

> I still think pointing to extensions is of value. In general users
> with unsupported extensions need to be pushed into testing their bug
> without the broken extension before we hear about it.
> 
> (This code dramatically reduced noise on the bugtracker from broken
> third-party extensions.)
> 
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at selenic.com
>> https://selenic.com/mailman/listinfo/mercurial-devel
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel



pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock



More information about the Mercurial-devel mailing list