answers.log contains incomplete or malformed lines

未關閉
#2,016 13 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 4 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
22/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
perl
領域
backend

研究方向

The payload names no source file, so start by searching the repository for where answers.log is written and which code path logs each answer. The sample lines show a broken record: a newline inside an answer field splits the entry, and some lines lack the timestamp prefix. Done means the logger writes one well-formed line per answer, reproduced with input that contains newlines.

由索引模型根據 Issue 內容生成。

描述

Here are 3 consecutive lines from the file answers.log in my course:

[Thu Mar 09 21:48:44 2023] |ZI7UJNQDCR03|WW06|18|100    1678427324      -ky
x+32)/2
[Thu Mar 09 21:48:44 2023] |7XTJHYSEKZ08|WW06|13|100000 1678427324      tan(arctanx)    [0,pi]

Here are 3 others:

[Thu Mar 09 21:49:11 2023] |C93SRBEKNW04|WW06|19|1110   1678427351      7       1       3       3.67
8(T-22) 106.3
[Thu Mar 09 21:49:12 2023] |BA05O2XZTR07|WW06|13|111000 1678427352      x       (-inf,inf)      tan(arctanx+arctan(-5))

In both cases there is something wrong with the line in the middle. My answers.log file has 1326 lines that don't have the expected structure, out of 3052734 lines in total. For many of these, including the two examples shown above, the lines before and after show timestamps that are very close together (sometimes identical).

Unfortunately I do not have the knowledge or skill to help fix this. All I can do is report it. Thanks for reading.

I harvested the file named "answers.log" from the File Manager in the user-facing web interface. To make sure I got a valid copy I downloaded the file twice. Both copies (size 301MB) show the same md5 hash.

This is WeBWorK © 1996-2022 | theme: math4 | ww_version: 2.17 | pg_version 2.17

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