-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible error #82
Comments
I think this issue has been fixed in 0.4.1 currently we are using 0.4.0 |
I wouldn't worry about it. It's just a deprecation warning. We can update to the newer version of djoser to make it go away. We just need to check what other changes have been made to djoser: from the commit log, it all looks pretty benign. You could try upgrading to the latest version (0.4.3) and seeing whether all our tests still work. (I'll do that on Monday if you don't get to it before me.) |
@eomwandho + @ian-ross did either of you get a chance to try the upgrade? (I don't think this is urgent, just was going to close the ticket though if it wasn't pending) |
Fixed at some point: djoser is now at 0.4.3. |
After the upgrading djoser, the error no long shows. |
I keep getting this error when running vagrant up. Even after doing vagrant destroy and deleting the env/ folder.
What could be the issue
The text was updated successfully, but these errors were encountered: