5d9f2fe12f
JIRA: MST-736 Due to inconsistencies in the way we handle attempts in past due practice proctored/onboarding exams, learners can end up in an unintended liminal state after attempting to reset their onboarding attempt. If a learner attempts to reset their rejected onboarding attempt after the exam's due date, we process the reset request and move their attempt into the "onboarding_reset" state. Theoretically, a new exam attempt should be created immediately thereafter. However, we have code that prevents the creation of an exam attempt after the exam's due date, so the call to create a subsequent exam attempt fails, leaving the learner with an exam attempt with the "onboarding_reset" status. Theoretically, this situation should never occur, and the fact that it does is a bug. Because of this, we did not handle the "onboarding_reset" status in the StudentOnboardingStatus panel, and this status appears as "null". As an intermediate step, while we think about our due date logic, this pull request bumps the edx-proctoring library to version 3.8.5, which adds a new onboarding status "onboarding_status_past_due". This status is displayed as "Onboarding Reset Failed Due to Past Due Exam" in the StudentOnboardingPanel in the InstructorDashboard, which should provide course staff with a clearer explanation. JIRA: MST-745 tracks the removal of this intermediate code from the code base once we fix the underlying cause of this bug. JIRA: MST-749 tracks the fix for the behavior that allowed for this state to occur.
These directories specify the Python (and system) dependencies for the LMS and Studio. - ``edx`` contains the normal Python requirements files - ``edx-sandbox`` contains the requirements files for Codejail - ``constraints.txt`` is shared between the two (In a normal `OEP-18`_-compliant repository, the ``*.in`` and ``*.txt`` files would be directly in the requirements directory.) .. _OEP-18: https://github.com/edx/open-edx-proposals/blob/master/oeps/oep-0018-bp-python-dependencies.rst