Workaround for issue described in #250