The new 3.1.19 release raises this issue on my site: 
The new 3.1.19 release raises this issue on my site: