Lua/LaTeX: plenary's `-c "PlenaryBustedDirectory …"` is credited as busted's -c coverage flag (luacov false positive); Teal (.tl, tl check) unknown; l3build unknown; Neovim versions are the toolchain axis of a plugin
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 22/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 領域
- testing-qa, tooling
調査の方向性
Four separate detection problems are bundled here. Start with _luacov in project_validator/ecosystems/lua.py, where nvim's -c is read as busted's coverage flag, then the Lua toolchain_patterns call and the LaTeX toolchain_patterns in ecosystems/latex.py. Each finding needs its own fix and a corpus entry in corpus/ showing the expected result. Split the issue before starting, since the luacov fix and the matrix or LaTeX detection changes are independent.
索引モデルが issue の本文から書いたものです。
説明
telescope.nvim: coverage PASS "line coverage is reported with luacov" with no luacov anywhere — _luacov in ecosystems/lua.py takes nvim's -c as busted's coverage flag (affects every plenary-based plugin). luarocks' sources are Teal (117 .tl under src/luarocks/, the .lua beside them generated by tl gen; tl check is a type checker) → unrecognised, type-checking FAIL. latex3/l3build's regression tests (texlua l3build.lua check, .lvt/.tlg) on five engines → "no CI runs latexmk". telescope's matrix is 3 OSes × 2 Neovim versions (rhysd/action-setup-vim version:) → "1 Lua version (default)".
Evidence from the corpus audit
nvim-telescope/telescope.nvim / coverage
- kind: FALSE_POSITIVE
- actual: PASS: line coverage is reported with luacov
- expected: FAIL: nothing in the repository mentions luacov or
--coverage; CI only runs plenary's busted inside Neovim. - evidence:
Makefile:4:nvim --headless --noplugin -u scripts/minimal_init.vim -c "PlenaryBustedDirectory lua/tests/automated/ { minimal_init = './scripts/minimal_init.vim' }";
.github/workflows/ci.yml:48:make test;grep -rn luacovover the checkout finds nothing;
--answersfor coverage records"tools": ["luacov"],"reported": ["luacov"].
Validator:project_validator/ecosystems/lua.py_luacov:if not _runs_busted(command): return None(true via
_plenary, which matchesnvim+PlenaryBusted), thenif has_option(argv, "--coverage", "-c"): return reported(Granularity.LINE):
nvim's-c <command>is taken for busted's-c(coverage). - repro:
Makefilewithtest:\n\tnvim --headless -c "PlenaryBustedDirectory tests", a workflow steprun: make test,
onetests/a_spec.luacontainingdescribe(. - confidence: high
latex3/l3build / tests-run (and detection)
- kind: UNSUPPORTED
- actual: FAIL: LaTeX: tests found in 3 file(s), but no CI configuration runs latexmk -pdf main.tex (...); Lua: no tests found
- expected: PASS: CI runs the project's regression tests with l3build on five engines, and typesets the docs with it.
- evidence:
.github/workflows/main.yaml:27:run: texlua l3build.lua check -q -H --show-log-on-error;
.github/workflows/main.yaml:43:run: texlua l3build.lua doc -q -H;.github/workflows/main.yaml:21:
uses: zauguin/install-texlive@v4;build.lua:9:checkengines = {"pdftex", "xetex", "luatex", "ptex", "uptex"};
test filestestfiles/00-test-1.lvt,testfiles/00-test-1.tlg(map:.tlg20 files and.lvt11 files
"unrecognised";.ins9 files unrecognised here and 1 in mtheme: docstrip installers are LaTeX sources).
The map's CI jobs show"ecosystems": []for every job: neithertexlua,l3buildnorzauguin/install-texlive
is a LaTeX toolchain marker (project_validator/ecosystems/latex.pytoolchain_patterns(... programs=("latexmk", "pdflatex", ...), actions=("latex-action", "setup-texlive-action"))).
l3build is how latex3 and most CTAN packages test (l3build check), so this misses the LaTeX ecosystem's main test
tool; thecheckengineslist is also the natural "toolchain matrix" for LaTeX, whichplatform-matrixcould count. - repro:
build.luawithmodule = "x",testfiles/a.lvt+testfiles/a.tlg, workflow steprun: l3build check
(ortexlua l3build.lua check) afteruses: zauguin/install-texlive@v4. - confidence: high
luarocks/luarocks / detection (Teal)
- kind: UNSUPPORTED
- actual: map
unrecognised_suffixes:.tl117 files;type-checkingFAIL "no type checker runs";committed-artifacts
"Lua: no build outputs are committed" - expected: Teal recognised as the project's source language:
.tlundersrc/luarocks/are the sources, the
.luabeside them are generated (tl gen), andtl check/tl gen --checkis a type checker. - evidence:
src/luarocks/build.tl,src/luarocks/cmd.tl, ... (27.tlbeside 27 generated.luainsrc/luarocks/
alone);tlconfig.lua:1-6:return {/build_dir = "build",/source_dir = "src",/include_dir = { "src", "types", "vendor" },/gen_target = "5.1",;
teal.sh:12:tl gen --check -I ../types -I ../vendor $tealname -o $luaname;.github/workflows/test.yml:71:
luarocks install tl;vendor/argparse.d.tl,vendor/dkjson.d.tl(Teal declaration files).
Not a bug: Teal is simply not in the Lua profile (nor is.moonMoonScript: busted'sspec/moonscript_spec.moon). - repro: unclear (new language support)
- confidence: medium
nvim-telescope/telescope.nvim / platform-matrix
- kind: FALSE_NEGATIVE
- actual: FAIL: CI covers 1 OS(es) (linux), 1 Lua version(s) (default), 1 combination(s); detail lines list six
unit tests (...)jobs on linux, macos and windows, each "no Lua version" - expected: PASS: the test matrix is 3 OSes x 2 Neovim versions (nightly, stable); for a Neovim plugin the runtime
version is the toolchain axis, named byrhysd/action-setup-vim'sversion(alsoneovim: true), or by
folke/github/neovim's /MunifTanjim/setup-neovim-action's inputs. - evidence:
.github/workflows/ci.yml:19-20:os: [ubuntu-latest, macos-latest, windows-latest]/rev: [nightly, stable];
.github/workflows/ci.yml:32-35:uses: rhysd/action-setup-vim@v1/with:/neovim: true/version: ${{ matrix.rev }}.
Validator:project_validator/ecosystems/lua.pytoolchain_patterns("Lua", version=_LUA_VERSION, inputs=("luaVersion", "lua-version"), ... actions=("gh-actions-lua",))
knows only Lua interpreter versions. The one counted job is the luacheck job (lint.yml:23:sudo luarocks install luacheck, version "default"). - repro: workflow with
matrix: {os: [ubuntu-latest, macos-latest], rev: [stable, nightly]}, step
uses: rhysd/action-setup-vim@v1withneovim: true,version: ${{ matrix.rev }}, thenrun: nvim --headless -c "PlenaryBustedDirectory tests". - 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分
- マージ済み 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 日以内に返信