Latest 2.0.22 pre-release causes this error on init. No special test case needed, it just fails right out of the box.