This issue is due to a major oversight from the fork - a fix will be available shortly.