[QTI] Remove the server wait for possibly stale cached assessment items
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 25/100
Línea de trabajo
Read the startup cleanup and its tests from issue #6340, then identify the EditModal test that checks complete when loading fails. Remove the startup cleanup and its cleanup tests while preserving that EditModal behavior; done means startup no longer touches the assessment item table and the acceptance criteria pass. The issue says this work is not open for contribution, so find a suitable issue through the contributing guidelines.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Overview
This is a reminder. The checks from #6340 only matter while caches may hold legacy items, or edits from tabs still on the old assets. Both come from the weeks around the QTI release. Once active users have opened their exercises on the new assets, remove them.
Part of #6337. Ships in the cleanup release: the first hotfixes release after the QTI release has been in production for about a month.
Complexity: Low
Target branch: hotfixes
Context
- #6340 makes
loadAssessmentItemswait for the server on an exercise's first open after a page load, and when its cached items include a legacy one. - An exercise that isn't opened between the QTI release and the cleanup release keeps its cached legacy items. When it's opened, the background refresh updates IndexedDB but not the open exercise, so its legacy items show as unsupported until it's reopened.
The Change
- Delete #6340's checks and their tests.
Acceptance Criteria
-
loadAssessmentItemsno longer waits for the server on a first open after a page load, or when cached items are legacy - #6340's tests are removed
AI usage
I outlined the approach. Claude drafted the issue, which I then checked and corrected for accuracy.
- Lenguaje dominante
- Python
- Estrellas
- 212
- Forks
- 321
- Merge medio
- 1 d 7 h
- PR fusionados (30 d)
- 14
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de learningequality/studio
-
Community library status changes don't update `date_updated`Posiblemente ocupada @ArpitaSamanta10 la tomó hoy. Abiertocommunity-contribution-in-progress DEV: backend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
learningequality/studio#6414 · 8 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
DEV: backend
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
learningequality/studio#6410 ·
Los mantenedores suelen responder en 1 día
-
DEV: backend
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
learningequality/studio#6409 ·
Los mantenedores suelen responder en 1 día
-
DEV: backend
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
learningequality/studio#6407 ·
Los mantenedores suelen responder en 1 día
-
Stripe webhook accepts events when no webhook secret is configuredPosiblemente ocupada @adibmbrk la tomó hoy. Abiertocommunity-contribution-in-progress DEV: backend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
learningequality/studio#6404 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de learningequality/studio
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días
-
Reference check: findingsAbiertoaudit-reference-check
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
screenrec.com stopped workingAbiertosite-bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
canonical/paas-charm#407 · 1 comentario ·
Los mantenedores suelen responder en 5 días