BEAM: Gleam is unknown (gleam.toml, .gleam, gleam test/format), erlang.mk is not a build system (rebar.config is its generated artifact), Earthly targets
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 25/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- github-actions, python
- 領域
- build-system, ci-cd
調査の方向性
The issue spans three separate detection gaps: Gleam files and gleam.toml, erlang.mk versus the generated rebar.config, and Earthly targets in CI. Start with the corpus expected results under corpus/ (projects.toml, and the gleam-lang/stdlib, ninenines/cowboy and elixir-ecto/ecto entries) and the detection code they exercise. Done means those three projects produce the expected build systems, test and format results, and no silent gaps, with the corpus results updated to match.
索引モデルが issue の本文から書いたものです。
説明
gleam-lang/stdlib: 42 .gleam files unrecognised, judged as Erlang + JavaScript from its FFI shims; gleam test and gleam format --check in every job → tests-run and code-formatting FAIL. cowboy: build_systems: ["rebar3"] from a rebar.config erlang.mk generates for Hex; deps are pinned in the Makefile, outputs are ebin/, deps/, .erlang.mk/ (all ignored), compiled with -Werror by erlang.mk → three wrong WARNs. ecto's integration tests run through earthly +integration-test (a committed Earthfile running mix test), neither read nor unknown.
Evidence from the corpus audit
gleam-lang/stdlib / detection (and tests-run, code-formatting, static-analysis, platform-matrix)
- kind: UNSUPPORTED (DETECTION)
- actual: map: languages
Erlang, JavaScript, build_systems[], unrecognised.gleamx42; tests-run FAIL "BEAM: no
tests found ...; JavaScript/TypeScript: no tests found"; code-formatting FAIL "CI never runs erlfmt ... prettier" - expected: a Gleam (BEAM) project with build system
gleam(gleam.toml), tests-run PASS (gleam testin every
job), code-formatting PASS (gleam format --check), and no JavaScript/TypeScript judgement for the 5 FFI.mjs
files - evidence:
gleam.toml:1:name = "gleam_stdlib";.github/workflows/ci.yml:32:- run: gleam test --target erlang;
.github/workflows/ci.yml:33:- run: gleam format --check src test;ci.yml:51:gleam test --target javascript --runtime node;test/gleam_stdlib_test.gleamexists;grep -rli gleam project_validator docs README.mdreturns
nothing. The 42.gleamfiles are the whole product; the detected "Erlang" (5.erl) and "JavaScript" (5.mjs)
are FFI shims. - repro:
gleam.toml+src/a.gleam+test/a_test.gleam+ workflowrun: gleam testandrun: gleam format --check src test - confidence: high
ninenines/cowboy / detection (build system), dependency-management, vcs-ignore, warnings-as-errors
- kind: DETECTION (UNSUPPORTED: erlang.mk)
- actual: map
build_systems: ["rebar3"]; dependency-management WARN "declared in rebar.config (rebar3) but not
locked"; vcs-ignore WARN ".gitignore does not ignore the _build directory"; warnings-as-errors FAIL "warnings are
not treated as errors in CI configuration or rebar.config" - expected: build system erlang.mk (the
rebar.configis an artifact erlang.mk generates for Hex); deps are pinned
by tag in the Makefile;_build/is rebar3's tree, erlang.mk's outputs (ebin/,deps/,.erlang.mk/) are all
ignored; erlang.mk compiles with-Werrorby default. - evidence:
Makefile:60:include erlang.mk;Makefile:89-91:# Generate rebar.config on build./app:: rebar.config;
Makefile:18-20:DEPS = cowlib ranch/dep_cowlib = git https://github.com/ninenines/cowlib 2.22.0;
.gitignore:.erlang.mk,deps,ebin/*.beam;erlang.mk:1626:ERLC_OPTS ?= -Werror +debug_info +warn_export_vars +warn_shadow_vars \;grep -rli erlang.mk project_validator docsreturns nothing. erlang.mk is
the build tool of cowboy, ranch, gun, cowlib and most ninenines/RabbitMQ-adjacent Erlang. - repro:
MakefilewithPROJECT = x+include erlang.mk, a committederlang.mk, a generatedrebar.config - confidence: medium (the judgements are defensible for a rebar3 user; the detection is what is wrong)
elixir-ecto/ecto / tests-run (integration tests under Earthly)
- kind: UNSUPPORTED
- actual: tests-run PASS (from the unit-test job); the integration-test job's
earthly ... +integration-testis
neither read nor reported as unknown (ecto.txt has no ERROR at all) - expected: either read the committed
Earthfiletarget (it runsmix testandmix test.all), or an ERROR "the
command earthly ... is not read" in strict mode; today the job silently contributes nothing. - evidence:
.github/workflows/ci.yml:80:run: earthly -P --ci --build-arg ELIXIR_BASE=${{matrix.elixirbase}} +integration-test;Earthfile:32-39:integration-test:...RUN mix test;Earthfile:79:mix test.all;;
grep -rli earthly project_validator docsreturns nothing. - repro: workflow
run: earthly +testwith anEarthfiletargettest:/RUN mix test - confidence: medium (Earthly is niche outside the Elixir core projects; the silent part is the real point)
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 日以内に返信