@jramnai I just bumped into a discussion related to this, with a possible fix incoming.
Please review the comments on this PR: