Thanks for the bug report, @nathank!
I’ve just merged a fix for this:
Let me know if this fixes the issue for you, or if you run into any further problems!