C/C++ tools not recognised: cmake-format/gersemi, astyle, Coverity Scan, scan-build as an analyzer job, OpenCppCoverage, uncrustify, tools driven by `zig build`, MinGW hardening flags
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
調査の方向性
Start in the project_validator/ package, where the grep -rn cmake-format project_validator/ check finds nothing, and find how the C/C++ profile detects formatters, static analyzers, coverage tools and hardening flags. Each listed tool needs a recognition rule and a note or WARN credit, with the nlohmann astyle message corrected. Done means the corpus cases named in the issue now produce the expected results, and the existing tests still pass.
索引モデルが issue の本文から書いたものです。
説明
fmt's CI job formats CMake files with cmake-format and fails on a diff (invisible); nlohmann/json defines its style in tools/astyle/.astylerc and CI fails when astyle changes the headers ("formatting is not defined" is wrong even if astyle stays unsupported); dbus-broker, nlohmann and glib run Coverity Scan jobs; glib and neovim run the Clang Static Analyzer (scan-build) as a CI job ("no static analyzer runs"); cmake_template and Catch2 run OpenCppCoverage on Windows (--export_type cobertura:); neovim runs clang-tidy and uncrustify through zig build targets in build.zig, and emmylua_check for Lua types; glfw links the MinGW equivalents of /DYNAMICBASE/DEP.
Evidence from the corpus audit
fmtlib/fmt, cpp-best-practices/cmake_template / code-formatting (cmake-format)
- kind: UNSUPPORTED
- actual: no mention; fmt's CI job that formats CMake files and fails on a diff is invisible.
- expected: cmake-format (cmakelang) / gersemi recognised as CMake-file formatters, at least as evidence.
- evidence: fmt .github/workflows/lint.yml:33
cmake-format:; :43-45:find . -name CMakeLists.txt -o -name '*.cmake' | \/xargs cmake-format -i/git diff --exit-code; fmt.cmake-format; cmake_template
.cmake-format.yaml.grep -rn cmake-format project_validator/finds nothing. - repro: n/a (gap)
- confidence: high
nlohmann/json / code-formatting (astyle)
- kind: UNSUPPORTED
- actual: FAIL: "C/C++: no clang-format configuration found; formatting is not defined"
- expected: the project defines its style in
tools/astyle/.astylercand CI fails when astyle changes the
amalgamated headers (check_amalgamation.yml ->ci_test_amalgamation); "formatting is not defined" is wrong even
if astyle stays unsupported. - evidence: cmake/ci.cmake:446:
COMMAND venv_astyle/bin/astyle --project=tools/astyle/.astylerc --suffix=none ${include_dir}/json.hpp ...; Makefile:90:ASTYLE=tools/astyle/venv/bin/astyle; .github/workflows/check_amalgamation.yml. - repro: n/a (gap)
- confidence: high
bus1/dbus-broker, nlohmann/json / static-analysis (Coverity Scan)
- kind: UNSUPPORTED
- actual: dbus-broker "C/C++: no static analyzer runs"
- expected: Coverity Scan is a static analyzer common in C projects; a scheduled
make coverity-scan/
cov-buildjob deserves at least a WARN-level credit. - evidence: dbus-broker .github/workflows/coverity.yml:48:
run: make coverity-scan; :51:run: make coverity-upload
(targets in the top-level Makefile); nlohmann README shows a Coverity Scan badge (status-badges names it). - repro: n/a (gap)
- confidence: medium
cpp-best-practices/cmake_template, catchorg/Catch2 / coverage (OpenCppCoverage)
- kind: UNSUPPORTED
- actual: no mention of the Windows coverage runs (cmake_template PASSes on gcovr anyway; Catch2's appveyor is
heuristic). - expected: OpenCppCoverage (
--export_type cobertura:) recognised as a Windows coverage tool. - evidence: cmake_template .github/workflows/ci.yml:185:
OpenCppCoverage.exe --export_type cobertura:coverage.xml --cover_children -- ctest -C ${{matrix.build_type}}; Catch2 appveyor.yml:22:
.\tools\misc\installOpenCppCoverage.ps1. - repro: n/a (gap)
- confidence: medium
GNOME/glib, neovim/neovim / static-analysis (scan-build, Coverity)
- kind: UNSUPPORTED
- actual: glib FAIL "C/C++: no static analyzer runs"; neovim FAIL "clang-tidy is configured (.clang-tidy) but does not run"
- expected: note only: both run the Clang Static Analyzer (scan-build) as a CI job, and glib has a Coverity job; the C/C++ profile accepts only clang-tidy and cppcheck.
- evidence: glib
.gitlab-ci.yml:1140:- SCANBUILD="$(pwd)/.gitlab-ci/scan-build.sh" ninja -C _scan_build scan-build;:1175:"${HOME}"/cov-analysis-linux64-*/bin/cov-build --dir cov-int meson compile -C _coverity_build; neovim.github/workflows/test.yml:135:- run: cmake --build build --target clang-analyzer. - repro: n/a (gap)
- confidence: high
neovim/neovim / tools driven by zig build, uncrustify, emmylua
- kind: UNSUPPORTED
- actual: static-analysis "clang-tidy is configured (.clang-tidy) but does not run"; code-formatting "C/C++: .clang-format is defined but CI does not run clang-format"; type-checking "Lua: lua-language-server is configured (.luarc.json) but does not run"
- expected: note only: clang-tidy and the C formatter (uncrustify, not clang-format) run through
zig buildtargets defined inbuild.zig; Lua type checking runs with emmylua_check (emmylua-checktarget,.emmyrc.json), not lua-language-server. - evidence:
.github/workflows/test.yml:61:run: zig build lintc-clang-tidy $OPTS;:65:run: zig build lintc-uncrustify $OPTS;:109:run: cmake --build build --target emmylua-check;src/nvim/CMakeLists.txt:966-967:COMMAND ${UNCRUSTIFY_PRG}/FLAGS -c ${UNCRUSTIFY_CONFIG} -q --check;.emmyrc.json;build.zig. - repro: n/a (gap;
build.zigneeds a Zig evaluator) - confidence: high
glfw/glfw / hardening (MinGW link flags)
- kind: UNSUPPORTED
- actual: FAIL: "no hardening options found; ... /DYNAMICBASE, /CETCOMPAT"
- expected: note only: the MinGW equivalents of
/DYNAMICBASEand DEP are linked when available. - evidence:
src/CMakeLists.txt:300:target_link_libraries(glfw PRIVATE "-Wl,--nxcompat");:309:target_link_libraries(glfw PRIVATE "-Wl,--dynamicbase");:318:target_link_libraries(glfw PRIVATE "-Wl,--high-entropy-va"). - repro: n/a (gap)
- confidence: low
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分
- マージ済み PR(30日)
- 79
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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 日以内に返信