[QTI] Make unstable's migration graph match the migrations applied in production
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 20/100
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
❌ 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.
- 主要语言
- Python
- 星标
- 212
- 派生
- 321
- 平均合并
- 1 天 7 小时
- 30 天内合并 PR
- 14
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
learningequality/studio 的其他 Issue
-
Community library status changes don't update `date_updated`可能已有人在做 @LightCreator1007 于 1 天前认领。 未关闭DEV: backend good first issue help wanted
难度 2/5 1-3 小时 新手友好度 84/100
learningequality/studio#6414 · 3 条评论 ·
维护者通常 1 天内回复
-
DEV: backend
难度 2/5 1-3 小时 新手友好度 82/100
learningequality/studio#6410 ·
维护者通常 1 天内回复
-
DEV: backend
难度 2/5 1-3 小时 新手友好度 76/100
learningequality/studio#6409 ·
维护者通常 1 天内回复
-
DEV: backend
难度 2/5 1-3 小时 新手友好度 78/100
learningequality/studio#6407 ·
维护者通常 1 天内回复
-
DEV: backend good first issue help wanted
难度 2/5 1-3 小时 新手友好度 78/100
learningequality/studio#6404 · 1 条评论 ·
维护者通常 1 天内回复
查看 learningequality/studio 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
canonical/paas-charm#407 · 1 条评论 ·
维护者通常 5 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 90/100
FAIRmat-NFDI/pynxtools-spm#136 ·
维护者通常 1 天内回复
-
enhancement tooling
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
`read_nexus` entry point points to a function that no longer exists可能已有人在做 @RubelMozumder 今天认领。 未关闭annotator bug
难度 1/5 1 小时以内 新手友好度 88/100
FAIRmat-NFDI/pynxtools#876 · 1 条评论 ·
维护者通常 1 天内回复
-
[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 retrying可能已有人在做 @yipinghuang1991 今天认领。 未关闭comp/agent P2 type/bug
难度 2/5 1-3 小时 新手友好度 82/100
NousResearch/hermes-agent#156837 ·
维护者通常 1 天内回复