@fomenkoandrey, still getting this error when using 8.x-1.0?