Confirming this issue is still present with current TW as of today with the same logging errors posted in #13.