26 Jun
2019
26 Jun
'19
2:03 p.m.
On Jun 26, 2019, at 1:01 PM, Geaaru <geaaru@gmail.com> wrote:
I saw your patch on upstream and I dunno if your commits cover completely this use case.
It doesn't fix it.
But if could help, now I have a different stack for the exception with your last changes:
It now complains when the problem occurs, and not many functions later. I've tracked it down to exactly the situation that needs to be fixed. We should have a fix in a few days. Alan DeKok.