This is a problem in the latest weekly (v0.3.17.3), but there's a hotfix that came out immediately after (v0.3.17.4) that fixes it.
