Skip to content
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

Closed
eomwandho opened this issue Mar 5, 2016 · 5 comments
Closed

Ansible error #82

eomwandho opened this issue Mar 5, 2016 · 5 comments

Comments

@eomwandho
Copy link
Contributor

I keep getting this error when running vagrant up. Even after doing vagrant destroy and deleting the env/ folder.

What could be the issue

@eomwandho
Copy link
Contributor Author

I think this issue has been fixed in 0.4.1 currently we are using 0.4.0

@ian-ross
Copy link
Contributor

ian-ross commented Mar 5, 2016

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.)

@wonderchook
Copy link
Contributor

@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)

@ian-ross
Copy link
Contributor

Fixed at some point: djoser is now at 0.4.3.

@eomwandho
Copy link
Contributor Author

After the upgrading djoser, the error no long shows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants