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 platform includes jshint as a development tool, and our
builds are enforcing a limit on total number of jshint violations.
This commit will enforce no new jshint violations on a per-change
basis, much like pylint and pep8 are enforced. So with this change,
we'll be enforcing our linting requirements consistently, regardless
of type of violations.
Also on Jenkins, runs quality task after installing jshint.
The latest version of uglify-js fixed a vulnerability which allows a specially crafted Javascript file to have altered functionality after minification.
Changelog between the versions we are running can be found in the Readme file from this diff: https://github.com/mishoo/UglifyJS2/compare/v2.4.15...v2.4.24#diff-04c6e90faac2675aa89e2176d2eec7d8
We use the command line without any special arguments so I don't expect any issues.
CSRF protection needs to be disabled so that requests made using OAuth and other non-session-based authentication mechanisms can be properly processed. If session authentication is used, DRF will enforce CSRF protection.
XCOM-524
This is the default in 3.2, but will need to be explicitly stated in
Sass 3.4.
Also, added a --force parameter to compile_sass to make it easier to see
what warnings are current.
