In the issue it is mentioned, that this should go away with something in 
the deprecation warning. I just got the same as above with a recent 
v0.4.0-rc1 but only sometimes. Should i just post to the closed issue, or 
open my own?

Reply via email to