@Hooverdan Just doing a quick follow-up on your issue as a result of this thread.
As you already know, given you diagnosed it in your referenced issue. We now have this fixed in our 4.5.8-0 release as per the following now merged pull request:
with this link included in our recent release notes here on the forum:
Just to bring this thread to a conclusion.
Thanks again for reporting and researching this issue. As always much appreciated.