I had this same error when upgrading from 1.16 to 1.17. I'm not sure what got rid of it, but now that I'm upgrading from 1.17 to 1.18, I'm getting the error again - this time it's so much longer though.
Jasmine Smoot-Leyva
I had this same error when upgrading from 1.16 to 1.17. I'm not sure what got rid of it, but now that I'm upgrading from 1.17 to 1.18, I'm getting the error again - this time it's so much longer though.