Racket: Resyntax (the Racket static analyser/refactoring linter) runs in typed-racket and scribble CI; static-analysis SKIPs "not applicable to Racket"
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- tooling
调研方向
Start from the corpus audit entries in corpus/ (the expected results and corpus/projects.toml pins for the typed-racket and scribble checkouts) and find where the static-analysis check returns SKIP with "not applicable to Racket". The issue also cites the Racket profile docs, which claim no common linter exists. Done means the check reports on Racket repos that run Resyntax and the docs no longer contradict it, which may need a maintainer decision on the expected behaviour first.
由索引模型根据 Issue 内容生成。
描述
Both repos run Resyntax on every pull request (and a scheduled autofixer); the Racket profile docs say "no linter the validator knows is in common use", but Resyntax is used by racket/racket, typed-racket, scribble and others.
Evidence from the corpus audit
racket/typed-racket, racket/scribble / static-analysis
- kind: UNSUPPORTED
- actual: SKIP: not applicable to Racket
- expected: PASS: both repos run Resyntax, the Racket static analyser/refactoring linter, on every pull request (and a scheduled autofixer); the Racket profile docs say "no linter the validator knows is in common use", but Resyntax is used by racket/racket, typed-racket, scribble and rebellion's author (
jackfirth/create-resyntax-pull-request). - evidence:
racket__typed-racket/.github/workflows/resyntax-analyze.yml:49:run: xvfb-run racket -l- resyntax/cli analyze --local-git-repository . "origin/${GITHUB_BASE_REF}" --output-as-github-review --output-to-file ./resyntax-review.json;:38:packages: resyntax;racket__scribble/.github/workflows/resyntax-analyze.yml:49: same command;resyntax-autofixer.yml:33:uses: jackfirth/[email protected]. - repro: a workflow step
run: racket -l- resyntax/cli analyze --local-git-repository . origin/main. - confidence: medium
Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.
🤖 Generated with Claude Code
- 主要语言
- Python
- 星标
- 4
- 派生
- 1
- 平均合并
- 10 小时 41 分钟
- 30 天内合并 PR
- 79
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cpp-best-practices/project_validator 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
cpp-best-practices/project_validator#267 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
cpp-best-practices/project_validator#263 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
cpp-best-practices/project_validator#260 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
cpp-best-practices/project_validator#259 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
cpp-best-practices/project_validator#255 ·
维护者通常 1 天内回复
查看 cpp-best-practices/project_validator 的全部 Issue
相似的 Issue
-
plot_graph crashes when a mesh node has no m2m edge可能已有人在做 @tygvi 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
mllam/neural-lam#883 · 1 条评论 ·
维护者通常 2 天内回复
-
enhancement possible-duplicate
难度 1/5 1-3 小时 新手友好度 78/100
AOSSIE-Org/PictoPy#1715 · 2 条评论 ·
维护者通常 6 天内回复
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on them未关闭
难度 2/5 1-3 小时 新手友好度 72/100
NVIDIA/auto-ontology#511 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
ethereum/execution-specs#3996 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Project-N-E-K-O/N.E.K.O#3725 ·
维护者通常 1 天内回复