[QTI] Make unstable's migration graph match the migrations applied in production
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 20/100
Línea de trabajo
The issue identifies the migration graph and the relevant migrations: 0168_alter_assessmentitem_type, 0169_invitation_organization, and the leaf migrations named in the acceptance criteria. Read those migration files and Django’s migration documentation, then check the production and unstable histories described here. Done means both histories migrate successfully and makemigrations --check reports no changes; the issue says it is not open for contribution.
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
As unstable stands today, the QTI release will fail to deploy at migrate, so unstable's migration graph needs to match what production has applied.
- Production has applied
0168_alter_assessmentitem_typeon top of0167_file_size_bigint_expand. - Unstable's copy of 0168 depends on
0167_add_organization, which production has never applied. - Django refuses to migrate a database where an applied migration has an unapplied dependency, and raises
InconsistentMigrationHistory.
Part of #6337. Starts after the hotfixes → unstable merge that brings in 0169_file_size_bigint_swap, so it can be tested against production's full history. Must be in unstable before the QTI release is cut.
Complexity: Low
Target branch: unstable
Context
master/hotfixes:0166→0167_file_size_bigint_expand→0168_alter_assessmentitem_type→0169_file_size_bigint_swap.unstable:0166→0167_add_organization→0168_alter_assessmentitem_type→0169_invitation_organization.- On unstable,
0170_merge_20260717_0136merges0167_file_size_bigint_expandwith0169_invitation_organization. 0169_file_size_bigint_swapalso depends on 0168, and reaches unstable with the next hotfixes → unstable merge.- That merge leaves two leaf migrations, so the merge PR must add a merge migration: Django refuses to migrate without one, and CI's
makemigrations --checkfails. - The conflict is in unstable today. The hotfixes → unstable merge doesn't cause it, and doesn't fix it.
The Change
- Point unstable's 0168 back to
0167_file_size_bigint_expand, as in production. - Make
0169_invitation_organizationalso depend on0167_add_organization. It adds a foreign key toOrganization, and once 0168 stops depending on0167_add_organization, nothing else makes that table exist first.
Decisions
- Why change unstable's migrations, and not production's
django_migrationstable? It keeps the deploy free of manual steps.
Known gaps
- Local databases last migrated on
unstablebefore0170_merge_20260717_0136have unstable's 0168 applied without0167_file_size_bigint_expand, so they raiseInconsistentMigrationHistoryafter this change. Migrating them before pulling it, or resetting them, fixes that.
Acceptance Criteria
-
migratesucceeds on a database with production's history (0167_file_size_bigint_expand,0168_alter_assessmentitem_typeand0169_file_size_bigint_swapapplied) -
migratestill succeeds on a database that is already on unstable's history through0170_merge_20260717_0136 -
makemigrations --checkreports no changes
AI usage
Claude found this while comparing the migrations on
master,hotfixesandunstable, and 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
-
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
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
FAIRmat-NFDI/pynxtools-spm#136 ·
Los mantenedores suelen responder en 1 día
-
enhancement tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
`read_nexus` entry point points to a function that no longer existsPosiblemente ocupada @RubelMozumder la tomó hoy. Abiertoannotator bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
FAIRmat-NFDI/pynxtools#876 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: HTTP 499 (Client Closed Request) is classified as a non-retryable format_error, so a mid-flight abort fails the turn over instead of retryingPosiblemente ocupada @yipinghuang1991 la tomó hoy. Abiertocomp/agent P2 type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
NousResearch/hermes-agent#156837 ·
Los mantenedores suelen responder en 1 día