For those following the original issue, it is at this point considered resolved by a fix implemented in 1.46.1 (unless it occurs again...).