Problem renumbering after assigning a set

Abierto
#1,513 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
perl
Área
database

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Perl
Estrellas
164
Forks
167
Merge medio
6 d 7 h
PR fusionados (30 d)
27

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openwebwork/webwork2

Todos los issues de openwebwork/webwork2

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.