Alexey

I do not know, you tell me :) The bug was reproduced in November 2017. Did you fix it in new commits? Did you check it?

@skrusty No, I did not correct this bug in this project. I just went back to the earlier version of the project, where there was not this error. You do...