On 02/17/2020 06:59 PM, ori@eigenstate.org wrote:
>> Any way, any ideas on where I can put more fprints to track down which
>> bit of code is in the wrong?
> The first step: find as small a repro for this bug as you can. And then
> post it (ideally as a script) so that someeone else can test it.
>
I have attached small tar file of test, as I was testing using a config 
file, i have stripped down the test config to bare minimum


-- 
We need another plan