I hoped that Sam is has some input on this. Sorry for the confusion.
Unfortunately we only tested this with 1.34.
Therefore I can't comment on when the issue was introduced and whether it was a
We do want to get this working soon though, so I'll see if I can get a chance to look
at this next week and find a way to reliably reproduce the issue.