answer on the cusp of a close date

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

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
perl
领域
backend

调研方向

The payload names no source files, so begin by finding where WeBWorK records an answer submission after a problem set's close time, and where it sets the score status. Reproduce by submitting an answer a few seconds after the close time and compare the answer log line with the stored score and past-answer row. Done when a late submission is either credited consistently in every place or rejected consistently, and the maintainers have agreed which behavior is correct.

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

描述

A student submitted a correct answer to a question, but was not awarded credit (their score/status is still zero). But the answer submission made it into the past answer table, and it shows up when we load the page, including with the green indicating it is correct:

Screenshot 2024-07-24 at 4 51 45 PM

Here is what the past answer page shows:

Screenshot 2024-07-24 at 4 52 40 PM

Note the close time was 10:00pm. And here is the answer log entry:

[Sun Jul 21 22:00:25 2024] |student.name|11_3-Using_Technology_to_Explore_Functions_Selected_Exercises|45|1	1721624425	[0,1.1]

So it was 25 seconds late. I think this all indicates an inconsistency somewhere. 22:00:25 was too late for the status to be updated to 1, but not so late to prevent the log entry and past answer entry.

主要语言
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 摘要。