Conversation
@ubernostrum - how's this branch going? Are you updating more libraries from |
26df89b
to
de74f1e
Compare
Ping @ubernostrum - 8 days without an update here. 😦 |
Ok, I've found a series of issues that need to be addressed before moving along with this. That said, I think this looks great in general, lots of changes, but all worth it. We may end up in the present eventually!! |
I've cleaned up most of the submodule version issues (and even removed one!), but there are a few things that need further poking or decisions:
|
I investigated DRF and emailed the summary to dev-mdn (May also want to watch encode/django-rest-framework#2681 and encode/django-rest-framework#2684.) I suggest we update to 2.3.14 immediately, and probably 2.4.4 soon after. |
Also, mdn-dev and devdoc-writers confirm we can remove grappelli. |
#3109 is now merged, so this could rebase on master and then it's ready to run tests? |
WARNING: This commit breaks compatibility with Django 1.4. Many of the warnings from the linter are actually spurious/overzealous reminders about checking the existence of cleaned_data (bad), where we actually were checking for the presence of specific elements in cleaned_data (good), but which django-compat-lint can't handle. As such they were left as-is, and only the actually-relevant changes (which are fewer in number) have been made.
This clears all the non-spurious warnings/errors from the lint output; the primary change here is transaction handling, with the changes falling into three main areas: 1. Replacing old transaction decorators with the new 'atomic' one, since it provides the behavior we wanted. 2. Removing use of 'transaction.autocommit', since autocommit is now the default behavior of Django. 3. Rewriting the page-move task -- which is probably the trickiest transaction-related code -- to temporarily disable autocommit, manually manage the page-move transaction, and turn autocommit back on afterward.
b8b8f83
to
09e5560
Compare
I incorporated the fix for amqp connection in the vm. I ran the new intern client-side test suite against this branch and fixed a bug I found in the newsfeed template. (I also sent a PR to improve the intern test suite messages.) Only thing I know we have to do now is fix Travis CI. I'll work on that tomorrow. |
I'm using #3232 against this branch to let me test Travis builds without committing here (yet). I couldn't find a path to follow with running ansible connections to Travis CI localhost, so I started a python script that re-uses those same Jinja2 templates as ansible to install the |
When trying to follow vagrant install instructions, getting this at the submodule init step:
Not sure if that's an actual issue with submodules, or with the wifi I'm on (which has been messing with connections all week). |
I destroyed and re-built my vm last night and had no issue. Probably wifi connection. |
2924329 is wrong. |
woops, part of the sentence missing. ..I'm going to hardcode that path in the settings_test.py. |
…e MySQL collation installation steps.
So apparently there are problems with MySQL on Travis, travis-ci/travis-ci#2353 (reported by the author of the Ansible roles we're using for MySQL). So I'm going to uninstall the Travis provided MySQL and install the community server from MySQL itself (https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/index.html). Because I haven't explored a rabbit cave in recent weeks |
… django-upgrade-1116335
|
Another merge from master.
|
This is the tracking PR for upgrading kuma to Django 1.7. This PR contains our project meeting notes & tasks.
The process:
git fetch mozilla
get checkout mozilla/django-upgrade-1116335
git submodule sync && git submodule update --init
find . -name "*.pyc" | xargs rm -f
vagrant provision
./manage.py test 2> test-stderr.txt
Tasks for code:
django-statici18n
usagecompiled.txt
Tasks for deploy:
Anytime:
May 26
virtualenv
(bug 1148435)compiled.txt
requirements file into the newvirtualenv
June 2
err: fatal: destination path 'vendor/src/elasticsearch-dsl-py' already exists and is not an empty directory.
(cause)rm -rf vendor/src/elasticsearch-dsl-py
ImportError: cannot import name widgets
find . -name "*.pyc" | xargs rm -f
ImportError: No module named Image
ImportError: No module named git
django.db.utils.OperationalError: (1060, "Duplicate column name 'user_id'")
Unknown command: 'update_badges'
June 2-4
June 9
June 9
SyntaxError: invalid syntax
django.db.utils.OperationalError: (1060, "Duplicate column name 'user_id'")
Tasks for post-deploy:
vendor
scheme andpip
requirements usage)django-rest-framework