With no recent activity on this report, we will go ahead and close it out for now.
With the release of V3 around the corner, please let us know if you encounter the issue again in that version by submitting a new report including the output log and reproduction steps, so we can continue to look into this further.