- Course overviews will cache courses upon publish.
- Added management command to warm up cache.
- OAuth2 handler returns courses via course overviews.
Currently, there is a way to do so via opening the LTI tool in a new
page, this removes the one line of code that specifies that it is the
only way to do it. It allows the iframe’d version of the tool to be
able to receive such information if necessary.
The print_out_all_courses() routine consumes a ton of memory (2G and
causes noticable mongo usage spikes). This actually causes other
processes on production boxes to be memory starved and killed
(such as worker children on edge when this was run recently).
The behavior of this script on production is
* Print several hundred courses
* Ask if you want to delete the one you specified
* print several hundred courses minus one
On a sandbox with 5 courses, you could tell by eye that 1 is gone, but
not in production (or even in stage).
The original PLAT-619 ticket for this suggested printing a course
listing on error, but instead it always printed the course listing.
Even in the error case, hundreds of course ids is confusing and obscures
the error message saying that your course_id is invalid.
You should be getting the course id from the UI or from ./manage.py lms
dump_course_ids, not by searching a list.
Adjusted the test accordingly
Remove get_courses_keys
The old line:
from path import path
produced pylint errors because of the baroque way that path.py defined
"path". We tried to get them to change how they defined it, but they
deleted the name instead: https://github.com/jaraco/path.py/issues/102
(Jason then changed his mind, but this is a better way to use path.py,
it avoids the pylint error at least.)
Also added reset_test_case() and @modifies_courseware to SharedModuleStoreTestCase.
Revert "More verbose test builds in Jenkins, for debugging."
This reverts commit 58cade4cc4288335026649470a48b7bbca969ee8.
There's a move afoot to put assets inside individual Django apps,
instead of in upper-level "templates" directories. These i18n
configuration files have to take this into account.
.underscore files are easy to find by their unique file extension, so
the rule can be simple. Mako files are .html, so we have to be more
nuanced about it. We don't want to get pure HTML files, and we don't
want to get .html files for tests, even if they are Mako templates.
