@badsector1 it looks like this should be fixed in the minor update we’ll be pushing tomorrow. See @kamil’s comment on the Github issue here: