Keep the six-codebase migration-risk run as a labelled regression set
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
调研方向
Start with cli/tests/test_migration_risk.py and the release checklist to see how existing false alarm classes and release checks are represented. Then trace the orm-lens migration-risk --format json entry point and its output fields before designing the pinned corpus, labels, and comparison script. Done means all 407 findings are labelled, the script reports zero differences on the current release, and the release checklist includes the manual run.
由索引模型根据 Issue 内容生成。
描述
The run behind the 407-alarms write-up (NetBox, PostHog, authentik, Healthchecks, Plane, paperless-ngx) produced a verdict for every critical finding: 2 real, 405 false. The nine false-alarm classes are already cut down into tests in cli/tests/test_migration_risk.py, but the full run is not checked in, so a new class of false alarm would only show up if someone repeats the exercise by hand.
A reader on DEV suggested keeping it (comment): a real corpus with per-finding verdicts is a regression suite most linters never get.
What to build
- A pinned list of the six projects with the commit each was scanned at.
- A labelled file per project: one row per finding (
file,migration,operation,rule,severity) with a verdict (real/false) and, for false ones, which of the nine causes it was. - A script that checks out the pinned commits, runs
orm-lens migration-risk --format json, and diffs the result against the labels: new findings, findings that disappeared, severity changes. - Run it manually before releases at first; a scheduled CI job can come later, since cloning six large repos is slow.
Done when
- The labels for all 407 findings are in the repo.
- The script reports zero differences on the current release.
- The release checklist mentions running it.
- 主要语言
- Python
- 星标
- 84
- 派生
- 13
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FROWNINGdev/django-orm-lens 的其他 Issue
-
suggest-indexes proposes composite indexes that include the primary key or a unique field可能已有人在做 @bfs2021 今天认领。 未关闭bug good first issue python
难度 2/5 1-3 小时 新手友好度 82/100
FROWNINGdev/django-orm-lens#269 ·
-
`migration-risk` text output prints `app.None` for graph-level findings可能已有人在做 @phoenixbycaselka 今天认领。 未关闭bug good first issue python
难度 1/5 1-3 小时 新手友好度 88/100
FROWNINGdev/django-orm-lens#268 ·
-
Finish the Chinese rule reference — DOL001–DOL007可能重新可做 @harbinresearcher 于 64 天前认领，目前没有进行中的 PR。 未关闭documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 68/100
FROWNINGdev/django-orm-lens#81 · 2 条评论 ·
-
Fields inherited from Django's `AbstractBaseUser` / `PermissionsMixin` / `AbstractUser` are missing未关闭bug good first issue python
难度 3/5 1-2 天 新手友好度 62/100
FROWNINGdev/django-orm-lens#267 ·
-
bug good first issue python
难度 3/5 半天 新手友好度 78/100
FROWNINGdev/django-orm-lens#266 ·
查看 FROWNINGdev/django-orm-lens 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
gorakhargosh/watchdog#1462 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
openwisp/openwisp-monitoring#889 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
OpenFreeEnergy/Lomap#180 ·
-
难度 2/5 1-3 小时 新手友好度 62/100
roman-corgi/corgisim#327 ·
维护者通常 2 天内回复
-
agent:WSL bug code-review linux pri:medium sev:low tooling
难度 2/5 半天 新手友好度 62/100
维护者通常 1 天内回复