Thanks, I’ve reproduced this issue internally and we’ll look into it.
This will be fixed in 0.7.6c. Thanks for the report!