answer marked correct but score not recorded as 1

未关闭
#2,720 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
perl
领域
backend, database

调研方向

The payload names no files, so start by reproducing it: create a one-answer problem, submit a wrong answer and then the correct one, and compare the feedback with the stored problem score. Find where the score is written after a correct answer and why it stays at 0 when the feedback says correct. Done when the recorded score and the displayed overall score both reflect the latest correct submission.

由索引模型根据 Issue 内容生成。

描述

The following took place on my production server which is pretty close to the current tip of develop, plus a few customizations that I would think are irrelevant.

A student had a question in an assignment that was (still is) open. There is just one answer blank. They submitted an incorrect answer. Then on their second try, they submitted the correct answer. The feedback confirms that the answer is correct: there is a green check mark and the alert at the top of the page says "The answer is correct.". However the score was not recorded as 1 in the database. They still had 0 for their score and the bottom of the page included the messages "You have attempted this problem 2 times." and "Your overall recorded score is 0%." Returning to the question, it's the same as PG reassesses the most recent answer as correct. (Still the green check box and still those same messages.)

Perhaps I should have explored things more before taking action, but I enabled permissions so I could submit on their behalf, and I submitted their answer as it was. And that was accepted and changed their score to 100%. Now with the official record of three submissions.

What might explain this? Some failure of the database to record the score?

主要语言
Perl
星标
164
派生
167
平均合并
6 天 7 小时
30 天内合并 PR
27

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openwebwork/webwork2 的其他 Issue

查看 openwebwork/webwork2 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。