--map reports a language and its suffix as unrecognised at once (CUDA/.cu, Objective-C/.m) and lists files the profiles read (.freeze, .xctestplan, .resolved, .Plugin, .rda, .eex, .asciidoc, .tftpl, .zsh-theme)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
The suffix tables are in project_validator/ecosystems/beam.py (around line 516), terraform.py (around lines 171-172) and swift.py (the XCODE_TEST_SETTINGS and PACKAGE_RESOLVED readers); the upper-case .XSD mismatch is in facts/structure.py (around line 214) and xml_schemas.py. Start by choosing one unrecognised suffix, such as .tftpl, and claiming it in its profile, then run --map on a small fixture to see it leave unrecognised_suffixes. Several items are policy questions (whether a language and its suffix can both be reported, and whether rchk counts as static analysis), so confirm the direction with a maintainer before editing.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
glfw lists languages: ["C", "Objective-C"] and .m ×5 unrecognised; llama.cpp CUDA and .cu ×209. cabal.project.freeze (a documented Haskell lock file), *.xctestplan and Package.resolved (read by the Swift profile), META-INF/services/*.Plugin (Java ServiceLoader files), .rda/.rds/.RData/.Rraw/.Rout.save/Makevars.win (R), .eex/.heex/.app.src/.config/.spec/.asciidoc/.cheatmd (BEAM), .tftpl/.tpl (Terraform templates), .zsh-theme/.zunit, .feature (Cucumber) are reported as unknown suffixes. Either the profile claims them or the language is not claimed.
Evidence from the corpus audit
ninenines/cowboy, elixir-ecto/ecto, phoenixframework/phoenix / detection (BEAM-ecosystem suffixes)
- kind: DETECTION
- actual: unrecognised suffixes: cowboy
.asciidocx151,.configx15,.ezdocx3,.appx1,.specx1 (CT spec),
.dtlx1; phoenix.eexx156,.cheatmdx1; ecto.cheatmdx2 - expected:
.eex/.heex/.leex(EEx templates) and.app.src/.config/.spec(Erlang terms) belong to the BEAM
profile;.cheatmdis an ex_doc cheatsheet (documentation);.asciidocis documentation (see the README finding). - evidence: the
unrecognised_suffixesarrays in the three.map.jsonfiles;project_validator/ecosystems/beam.py:516:
source_suffixes={".ex": ELIXIR, ".exs": ELIXIR, ".erl": ERLANG, ".hrl": ERLANG} - repro: a Mix project with
lib/x.html.heexandguides/cheatsheets/x.cheatmd - confidence: medium (low impact;
data-wellformed/committed-artifactscould use.config/.app)
glfw/glfw, ggml-org/llama.cpp / detection (languages vs suffixes)
- kind: MESSAGE
- actual: glfw
.map.jsonlistslanguages: ["C", "Objective-C"]andunrecognised_suffixes: [{".m": 5}]; llama.cpp listsCUDAas a language and.cu(209),.cuh(96) as unrecognised. - expected: a language the map names should not also be reported as unrecognised files (or the language should not be claimed).
- evidence:
glfw__glfw.map.json:"languages": ["C", "Objective-C"],{"suffix": ".m", "files": 5};ggml-org__llama.cpp.map.json:"CUDA"in languages,{"suffix": ".cu", "files": 209}. - repro: a CMake project with
project(x C OBJC)and one.mfile. - confidence: low
PostgREST/postgrest, koalaman/shellcheck / map (unrecognised suffix .freeze)
- kind: MESSAGE
- actual:
.map.jsonunrecognised_suffixes:{"suffix": ".freeze", "files": 1}in both projects, while PostgREST'sdependency-managementsayslocked in cabal.project.freeze, stack.yaml.lock - expected:
cabal.project.freezeis a known Haskell lock file (docs/ecosystems/haskell.md: "commits cabal.project.freeze") and should not be listed as unrecognised; shellcheck's isbuilders/linux.armv6hf/cabal.project.freeze. - evidence:
PostgREST__postgrest/cabal.project.freeze(root);koalaman__shellcheck/builders/linux.armv6hf/cabal.project.freeze - repro: a Cabal package with
cabal.project.freeze; run--map - confidence: medium
Rdatatable/data.table, tidyverse/dplyr, r-lib/testthat / detection (R data files and R-specific analyzers)
- kind: UNSUPPORTED
- actual:
unrecognised_suffixes: data.table.Rraw(12),.Rdata(4),.RData(2),.save(2),.win(1 =Makevars.win); dplyr.rda(5); testthat.rds,.win. data.table'srchk.yaml(rchk, the R-API static analyser for C code), the Coccinelle lint job and.ci/lint.Rcustom linters are not recognised as static analysis. - expected:
.rda/.rds/.RData/.Rdata(serialised R data underdata/,inst/),.Rraw(data.table's test scripts),.Rout.save/Makevars.winare files of the R ecosystem and should not be reported as unrecognised; rchk is the standard analyser for R packages with C code and would be a naturalstatic-analysistool for R's native code. - evidence:
data/starwars.rda(dplyr);inst/tests/tests.Rraw,src/Makevars.win(data.table);.github/workflows/rchk.yaml:46-56:- name: Run rchk...- name: Confirm that rchk has no errors;.github/workflows/code-quality.yaml:74-78:Install Coccinelle/run: /usr/bin/sudo apt-get -y install coccinelle/- name: Lint. - repro: an R package with
data/x.rda; expect no unrecognised suffix. - confidence: medium
ohmyzsh/ohmyzsh / detection, tests-run
- kind: UNSUPPORTED
- actual:
.map.jsonunrecognised_suffixes:.zsh-themex144,.zunitx3;Shell: no tests found - expected:
.zsh-themefiles are zsh scripts (Shell);plugins/dotenv/tests/*.zunitare zunit tests (CI does not run them, so the FAIL stands, but the message "no tests found" is wrong). - evidence:
themes/*.zsh-theme(144 files);plugins/dotenv/tests/basic-parsing.zunit,security.zunit,compatibility.zunit;.github/workflows/main.yml:36:zsh -n "$file" || return 1(syntax check only). - repro: a
tests/a.zunitfile. - confidence: low
flyway/flyway / detection (META-INF/services)
- kind: DETECTION
- actual: map
unrecognised_suffixes:.Plugin40 files - expected: Java ServiceLoader provider files under
META-INF/services/are JVM resources, not unknown suffixes - evidence:
flyway-commandline/src/main/resources/META-INF/services/org.flywaydb.core.extensibility.Plugin;
validator:grep -rn META-INF project_validator/ecosystems/jvm/returns nothing - repro:
src/main/resources/META-INF/services/com.example.Spi - confidence: medium
Alamofire/Alamofire, pointfreeco/swift-composable-architecture, realm/SwiftLint / detection (unrecognised suffixes the profile reads)
- kind: MESSAGE
- actual:
--mapunrecognised_suffixeslists.xctestplan(Alamofire 5 files, TCA 1) and.resolved(TCA 2,
SwiftLint 1), yet the Swift profile reads*.xctestplanfor coverage settings andPackage.resolvedas the
lockfile (dependency-management PASS citesPackage.resolved). - expected: files a settings/lockfile reader consumes are recognised, not reported as unknown suffixes.
- evidence: project_validator/ecosystems/swift.py:179:
XCODE_TEST_SETTINGS = SettingsReader(name="Xcode", files=("*.xcscheme", "*.xctestplan"), ...);
swift.py:390:PACKAGE_RESOLVED = lockfile_reader(manager="SwiftPM", files=("Package.resolved",));
AlamofireTests/Test Plans/iOS.xctestplan; SwiftLint./Package.resolved. - repro: a Swift package with
Package.resolvedcommitted; run--map. - confidence: low
terraform-google-modules/terraform-google-kubernetes-engine, terraform-aws-modules/terraform-aws-eks / detection (suffixes)
- kind: UNSUPPORTED
- actual: map
unrecognised_suffixes: [{".tmpl": 16}, {".tftpl": 1}](GKE),[{".tpl": 8}](eks) - expected:
.tftplis Terraform's documented template-file suffix (fortemplatefile()), and.tplis its older convention; a Terraform profile should claim them (as templates, roletemplate). - evidence:
examples/safer_cluster_iap_bastion/templates/startup-script.tftpl; ekstemplates/al2023_user_data.tpl. Validator:ecosystems/terraform.py:171-172:source_suffixes={".tf": ..., ".tofu": ..., ".tfvars": ...},ambiguous_suffixes={".hcl": TERRAFORM}. - repro:
templates/x.tftplin a Terraform project; expect it recognised, not listed as unrecognised. - confidence: medium
ISO-TC211/XML / detection (.XSD suffix case)
- kind: DETECTION
- actual:
unrecognised_suffixeslists.XSD(4 files);data-wellformeddoes not parse them; yetschema-declared
judges them ("schemas.isotc211.org/19160/-4/aip/2.8.0/cov.XSD: no targetNamespace") - expected: one consistent treatment: either an upper-case suffix is the format (then it is parsed by data-wellformed
and not "unrecognised") or it is not (then schema-declared does not judge it). - evidence:
schemas.isotc211.org/19160/-4/aip/2.8.0/cov.XSD,schemas.isotc211.org/19156/-/onm/2.0.0.1/modelConsistency,xsd.XSD
(+ theirschemas.isotc211.orgWorkcopies). Validator:ecosystems/xml_schemas.py:xsd_filesuses
PurePosixPath(path).suffix.lower() == ".xsd";facts/structure.py:214known.get(PurePosixPath(path).suffix)
does not lower. - repro: a single
A.XSD. - 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
- Lenguaje dominante
- Python
- Estrellas
- 4
- Forks
- 1
- Merge medio
- 10 h 41 min
- PR fusionados (30 d)
- 79
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cpp-best-practices/project_validator
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
cpp-best-practices/project_validator#267 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
cpp-best-practices/project_validator#263 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
cpp-best-practices/project_validator#260 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
cpp-best-practices/project_validator#259 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
cpp-best-practices/project_validator#255 ·
Los mantenedores suelen responder en 1 día
Todos los issues de cpp-best-practices/project_validator
Issues similares
-
plot_graph crashes when a mesh node has no m2m edgePosiblemente ocupada @tygvi la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
mllam/neural-lam#883 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
enhancement possible-duplicate
Dificultad 1/5 1-3 horas Aptitud para principiantes 78/100
AOSSIE-Org/PictoPy#1715 · 2 comentarios ·
Los mantenedores suelen responder en 6 días
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on themAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NVIDIA/auto-ontology#511 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ethereum/execution-specs#3996 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Project-N-E-K-O/N.E.K.O#3725 ·
Los mantenedores suelen responder en 1 día