With this upgrade, a small piece of javascript was fixed so we pass milliseconds instead of seconds to vendor script to check the healthiness of the proctoring desktop app
A couple of these (*/static, */templates) may prove to be too noisy, but
most of them seem low-traffic enough. If we find any of these
directories to be unhelpful, we can/should remove them.
The user_tasks app is only needed by a cms feature.
However, it has been listed under INSTALLED_APPS
for both cms and lms because app-permissions only ran
in an lms context until recently.
Since app-permissions now creates the user_tasks_admin
group in a cms context, the app can be safely removed
from lms's INSTALLED_APPS.
TNL-8274
The edx-platform codebase already includes quite a few type annotations, but
they were not regularly checked. This may cause problems, when the annotations
themselves include errors (as we found out in some of the learning_sequences
annotations). So here, we add mypy as a dev requirement and introduce a make
command to run mypy regularly. Mypy runs on a very small portion of the total
edx-platform, as configured in mypy.ini. Our hope is that developers will add
more and more modules to this configuration file, until we can eventually run
mypy on the full code base.
See discussion: https://discuss.openedx.org/t/dev-notes-running-mypy-on-edx-platform/4860
This version of the edx-proctoring library includes a fix to a bug in the onboarding status panel. This bug was preventing the appearance of the onboarding panel in a learner's course outline if an onboarding exam in the course was inaccessible to the learner in such a way that the Learning Sequences API did not return schedule information for the sequence. An onboarding exam that is content gated by enrollment track to an enrollment track in which the learner is not enrolled is an example of this. The bug was that the StudentOnboardingStatusView was not taking into account that an inaccessible sequence might not have a schedule.
Story
=====
As an XBlock developer,
I want to know which XBlocks are installed
so I can debug (and know which to add to Advanced Settings in Studio).
Testing
=======
- `make studio-shell`
- `python scripts/xblock/list-installed.py`
Integration
===========
I plan to invoke this from `devstack` (after installing XBlocks).
Tickets
=======
Fixes CENG-95
Fixesstvstnfrd/openedx-meta#153
[refactor] change backfill date task to long running task
Change from a task that spins off multiple other tasks to a single long
running task. This will hopefully be way less heavy when this is ran in
production.
