Haskell: shelltestrunner, treefmt --ci (fourmolu/hlint/actionlint), nix-built wrapper commands (postgrest-*)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 25/100
研究方向
Start with project_validator/ecosystems/nix.py around line 83, the only place the payload shows treefmt, then grep project_validator/ for pytest, sphinx-build and shelltest to find where recognised test and lint commands are listed. The nix wrapper case needs a design decision about how to treat opaque nix-provided commands, so agree on that before coding. Done means the corpus results for PostgREST and hledger change as expected.
由索引模型根據 Issue 內容生成。
描述
hledger's 585 functional tests are shelltest files (*.test, unrecognised) run by every workflow; PostgREST runs fourmolu, hlint and actionlint through treefmt --ci (treefmt-nix config), and its spec/hasql/io tests, pytest, sphinx-build -b linkcheck and weeder through nix-built postgrest-* wrappers from a composite action's tools: input → code-formatting, static-analysis, ci-lint, tests-run and link-check all wrong. treefmt is a common multiplexer in Nix-managed repos (treefmt.toml / treefmt-nix).
Evidence from the corpus audit
PostgREST/postgrest / code-formatting, static-analysis, ci-lint (treefmt)
- kind: UNSUPPORTED
- actual:
code-formattingFAILHaskell: fourmolu.yaml is defined but CI does not run ormolu, fourmolu or stylish-haskell;static-analysisFAILHaskell: no static analyzer runs;ci-lintWARNCI does not lint its GitHub Actions configuration - expected: all three are run by
treefmt --ci(fails on unformatted files) with the treefmt-nix configuration enabling fourmolu, hlint and actionlint. treefmt (treefmt.toml / treefmt-nix) is a common multiplexer in Nix-managed repos; the validator knows the word only as a Nix formatter. - evidence:
.github/workflows/check.yaml:33-34:- name: Run treefmt/run: treefmt --ci;nix/treefmt.nix:26:programs.actionlint.enable = true;;:29-30:programs.fourmolu.enable = true;/programs.hlint.enable = true;;.github/actionlint.yml(actionlint config present);project_validator/ecosystems/nix.py:83:must take it: nixfmt, alejandra and treefmt do).(only mention) - repro:
treefmt.tomlwith[formatter.fourmolu] command = "fourmolu" options = ["--mode","check"]and a steprun: treefmt --ci - confidence: high
PostgREST/postgrest / tests-run, link-check, static-analysis (nix wrapper commands)
- kind: UNSUPPORTED
- actual:
tests-runFAILHaskell: tests found in 1 file(s), but no CI configuration runs cabal test (or stack test); Documentation site: ... no CI runs sphinx-build; Python: tests found in 14 file(s), but no CI configuration runs pytest;link-checkWARNno link check found in CI configuration;static-analysisHaskell: no static analyzer runs - expected: these all run, through nix-built
postgrest-*wrapper scripts provided by the./.github/actions/setup-nixcomposite action'stools:input: spec/hasql/io tests, pytest,sphinx-build -b linkcheck(scheduled workflow named Linkcheck), weeder. The commands are opaque to the validator (their bodies are innix/tools/*.nix), so this is a gap rather than a parser bug; a "nix-provided command" notion (or readingcheckedShellScriptbodies in nix/tools) would be needed. - evidence:
.github/workflows/test.yaml:103-116:run: postgrest-with-${{ matrix.pgVersion }} postgrest-test-spec...run: postgrest-with-${{ matrix.pgVersion }} postgrest-test-io -vv;nix/tools/tests.nix:116:${ioTestPython}/bin/pytest --ignore=test/io/test_big_schema.py --ignore=test/io/test_replica.py -v test/io;.github/workflows/linkcheck.yaml:3-5,25:schedule:/- cron: '1 2 * * 3'...run: postgrest-docs-linkcheck;nix/tools/docs.nix:175:${python}/bin/sphinx-build --color -b linkcheck . ../.docs-build;nix/tools/tests.nix:168:docs = "Run spec and io tests while collecting hpc coverage data. First runs weeder to detect dead code."; - repro: unclear (needs reading nix shell-script derivations)
- confidence: medium
simonmichael/hledger / tests-run (shelltestrunner)
- kind: UNSUPPORTED
- actual: Haskell
tests-runPASS viastack install --test, but the 585 functional tests are invisible:.map.jsonunrecognised_suffixes:{"suffix": ".test", "files": 585} - expected: shelltestrunner (
shelltest) is the standard functional-test runner for Haskell CLIs (hledger, pandoc-adjacent tools); recognisingshelltest <dir>and*.testfiles would make the Haskell test picture complete. - evidence:
.github/workflows/ci.yml:351:COLUMNS=80 $stack exec -- shelltest --execdir -j16 hledger/test -x /_ -x ledger-compat/ledger-baseline -x ledger-compat/ledger-regress -x ledger-compat/ledger-collected;hledger/test/cli/addons.test;grep -rn -i shelltest project_validator/→ no match - repro: n/a (gap)
- 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
-
難度 2/5 1-3 小時 新手友好度 66/100
deepchem/deepchem#5289 · 1 則留言 ·
維護者通常 2 天內回覆
-
難度 1/5 1 小時以內 新手友好度 75/100
-
難度 2/5 1-3 小時 新手友好度 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 則留言 ·
維護者通常 1 天內回覆
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affected可能已有人在做 @grelinfo 今天認領。 未關閉documentation priority:low size:S
難度 1/5 1 小時以內 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
alphacrack/readme2demo#293 ·