Problem renumbering after assigning a set

Aperta
#1,513 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
perl
Ambito
database

Direzione di ricerca

The bug sits in the renumbering path that rewrites the problem_user table, which the reporter says left the QUIZ_NAME,v1 rows with stale problem_id values. Start by finding where problems are renumbered and how set versions are stored in the problem_user database, and reproduce by renumbering a 10-problem set after it has been assigned. Done means the versioned rows stay aligned with the renumbered problems and results show all 10 problems.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

A colleague of mine did the following:

  1. Created a Gateway Quiz with 10 problems.
  2. Assigned it to his students.
  3. Noticed that the numbers were not sequential, so renumbered and saved. (Note: this order is important)
  4. After taking the quiz, neither him nor the students could see the results. There was an error about certain problems not assigned to the student. Additionally, the score was listed out of 7 (instead of the 10 problems assigned).

I tracked down the problem in the problem_user database, the lines with set_id with QUIZ_NAME,v1 versions had the originalproblem_ids and the QUIZ_NAME were the new ones and those aligned for 7 of the 10. I fixed this my manually reassigning all of the misaligned problem_ids.

Although I haven't dug into the code, I think the renumbering just didn't update the QUIZ_NAME,v1 lines in the DB. Although this is quite an edge case (may not have happened before), I'm noting this for a possible fix.

Lingua principale
Perl
Stelle
164
Fork
167
Merge medio
6g 7h
PR unite (30g)
27

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openwebwork/webwork2

Tutte le issue di openwebwork/webwork2

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.