[PATCH 1 of 5] repair: use ProgrammingError
Ryan McElroy
rm at fb.com
Tue Mar 28 14:59:53 EDT 2017
On 3/27/17 2:11 PM, Augie Fackler wrote:
> On Mon, Mar 27, 2017 at 09:18:55AM +0200, Pierre-Yves David wrote:
>> Sure, that seems like a good idea. Can you see to it ?
> It's a good idea, but I feel like the name "ProgrammingError" alone
> provides some clue as to what's going on, and the migration is good.
>
> Queued, I wouldn't mind a followup to make the hint generic to all
> ProgrammingError instances, but I'm not willing to block on it either.
FWIW, I agree that losing the hint is sad. How confident are we that
core won't have these errors? Can we blame all ProgrammingError
exceptions on extensions?
More information about the Mercurial-devel
mailing list