Closed isaacovercast closed 4 years ago
I haven't seen this in a long time... you did change the chunking code recently, could it be related?
No, it's something else. I'm actively debugging this with 2 people right now actually. I'm on the trail, but it's a weird bug, hard to pin down.
On Wed, Nov 6, 2019 at 12:38 AM Eaton Lab notifications@github.com wrote:
I haven't seen this in a long time... you did change the chunking code recently, could it be related?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dereneaton/ipyrad/issues/369?email_source=notifications&email_token=ABNSXP6B6JRDQ47FZAM4BM3QSH7VXA5CNFSM4JIX3RLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDEXGAY#issuecomment-550073091, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNSXP5LC5CPJFD3H44TTJ3QSH7VXANCNFSM4JIX3RLA .
I added some error handling to allow for some samples to fail step 5, for example if there are no consensus sequences in the sample then nrows will be 0 and the previous code would crash. Here it passes the error message back up to the parallel function and then just reports failure, rather than killing the entire run. Fixed in df4603d9eeb68bba4f9b204e9416e8e4946095d0
Reported by @nitishnarula and @richie_hodel in the gitter. Full ipyrad CLI output:
I have debugged it to the point of figuring out the following:
But can't get a grip on why any of those would ever be zero. WTF?!