#27391

We addressed the issue again in v351b8. Please give a try to it.