The warning seems to be limited to 3.4. The code has changed in 3.6 and the warning is no longer an issue. Hopefully the upstream patch will get a review soon.
The warning seems to be limited to 3.4. The code has changed in 3.6 and the warning is no longer an issue. Hopefully the upstream patch will get a review soon.