this looks like a bug can you please fill jira issues so it can be addressed.
Should be fixed - please, try latest master.
I've checked current master and problem is already solved (last week if I well remember).
So I've rejected the issue as "Out of Date"
Thanks again for the report