This has to be a bug on our end then. I created an issue here:
I will take a look at it this week, but if you happen to uncover anything before then
please add any details to the jira issue.
View the original post :
Reply to the post :