This corrects an issue where assessments were sometimes incorrectly associated with the wrong response. The behavior was caused because the POST request to the `peer_assess` handler only contained the feedback text/options and did _not_ include mention of which original response was being assessed. If the current workflow item is updated on the server _after_ the page first loads but _before_ the page is submitted, this submission will be incorrectly associated with the following response. Steps to reproduce: - Submit a response (User A). - Wait for peers to submit responses (User B and User C). - Load page with first peer response to be assessed (not not submit). - Open the same page again in a new tab. - In 1st tab, assess and submit assessment for User B. - In 2nd tab, assess and submit assessment for User B. - Notice that your assessment for User B's response is also applied to User C's response. This changeset does _not_ restore data retroactively. Fix TNL-680
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| static | Loading commit data... | |
| test | Loading commit data... | |
| __init__.py | Loading commit data... | |
| data_conversion.py | Loading commit data... | |
| defaults.py | Loading commit data... | |
| grade_mixin.py | Loading commit data... | |
| leaderboard_mixin.py | Loading commit data... | |
| lms_mixin.py | Loading commit data... | |
| message_mixin.py | Loading commit data... | |
| openassessmentblock.py | Loading commit data... | |
| peer_assessment_mixin.py | Loading commit data... | |
| resolve_dates.py | Loading commit data... | |
| schema.py | Loading commit data... | |
| self_assessment_mixin.py | Loading commit data... | |
| staff_info_mixin.py | Loading commit data... | |
| student_training_mixin.py | Loading commit data... | |
| studio_mixin.py | Loading commit data... | |
| submission_mixin.py | Loading commit data... | |
| validation.py | Loading commit data... | |
| workflow_mixin.py | Loading commit data... | |
| xml.py | Loading commit data... |