@fast-megabyte-33579 I'll be releasing a fix for that error message today in 1.4.0.dev9