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 |
---|---|---|
.tx | Loading commit data... | |
conf | Loading commit data... | |
docs/en_us | Loading commit data... | |
logs | Loading commit data... | |
openassessment | Loading commit data... | |
requirements | Loading commit data... | |
scripts | Loading commit data... | |
settings | Loading commit data... | |
storage | Loading commit data... | |
test | Loading commit data... | |
.coveragerc | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
AUTHORS | Loading commit data... | |
LICENSE | Loading commit data... | |
MANIFEST.in | Loading commit data... | |
Makefile | Loading commit data... | |
README.rst | Loading commit data... | |
apt-packages.txt | Loading commit data... | |
karma.conf.js | Loading commit data... | |
manage.py | Loading commit data... | |
package.json | Loading commit data... | |
setup.py | Loading commit data... | |
urls.py | Loading commit data... |