@boggild @recon @jplopez Thanks for reporting. We were able to reproduce the problem and are working on a fix.