Derived census pilot side depends on the JVM for declared pilot-nondeterministic cells
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 40/100
Línea de trabajo
Start with tools/referee/apijson/nondeterminism.go, which declares the (FeatureChainExpression, featuringType) pair, then read tools/census/derived/pilot.go where the pilot value or empty is currently counted. Reproduce by running go run -C tools ./cmd/derived-census -check -require-exporter under two JDKs and comparing the pilot-examples row for Feature::featuringType. Done when the declared cells are scored apart from value and empty, sourced from the referee's declaration, and the committed records pass under both JVMs.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened, and what you expected instead
The pilot column of the derived-property census depends on the JVM that runs the pilot JSON exporter, so derived-census -check -require-exporter reproduces the committed records on one Java version and fails on another. The check should hold on any JVM, as pilot-apijson-diff -check does.
Measured at pin 2026-09 (artifact 0.63.0) on one tree, with the same exporter build, changing only the java first on PATH:
| JVM | Feature::featuringType, pilot-examples: pilot.value |
pilot.empty |
|---|---|---|
| OpenJDK 21.0.13 | 14548 | 1315 |
| Temurin 25.0.4 | 14551 | 1312 |
Each result is stable across repeated runs on its JVM, and it is the only record that differs between the two. Our side of the record does not move.
The three elements are FeatureChainExpressions in examples/pilot-corpora/sysml-examples/Interaction Sequencing Examples/ServerSequenceModelOutside.sysml, the values bound in PubSubSequenceOutside to:
server::publish_target_event = publish_message.doneserver::deliver_source_event = deliver_message.startconsumer::deliver_target_event = deliver_message.done
Under Java 21 their featuringType is empty; under Java 25 each has one. ServerSequenceOutsideRealization-2.sysml and -3.sysml re-export the same elements, which the census counts once by id.
The API-JSON referee already declares this: tools/referee/apijson/nondeterminism.go lists (FeatureChainExpression, featuringType) with the evidence and scores the row in a pilot-nondeterministic column, and docs/project/api-json-differential.md ("Declared pilot nondeterminism") gives the cause — the pilot fills an expression's implicit featuring types while its owner is transformed, so the value follows transformation order rather than the model. tools/census/derived has no such handling: pilot.go counts the property as a value or as empty, so the committed cell records whichever JVM ran -update.
The exporter launcher (build/pilot-json-exporter/export-json, written by scripts/download-pilot-json-exporter.sh) runs the first java on PATH and accepts any version from 21 up.
Reproduction
./scripts/download-pilot-corpora.sh # with the other corpus downloads
./scripts/download-pilot-json-exporter.sh
PATH=/path/to/jdk-21/bin:$PATH go run -C tools ./cmd/derived-census -check -require-exporter
PATH=/path/to/jdk-25/bin:$PATH go run -C tools ./cmd/derived-census -check -require-exporter
At most one of the two exits 0; the other reports Feature::featuringType for pilot-examples as moved.
Expected
The census scores the declared pilot-nondeterministic (metaclass, property) cells apart from value and empty, reading the referee's declaration rather than a second list, so the records reproduce under either JVM.
- Lenguaje dominante
- Go
- Estrellas
- 59
- Forks
- 20
- Merge medio
- 10 h 23 min
- PR fusionados (30 d)
- 897
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
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 Open-MBEE/OpenSysML
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
A model's parse is still paid cold in every process; the library record cache does not cover itAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 28/100
Los mantenedores suelen responder en 1 día
Todos los issues de Open-MBEE/OpenSysML
Issues similares
-
Missing Readme InstructionsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
OpenSlides/openslides-go#342 ·
Los mantenedores suelen responder en 4 días
-
docs: link to the CLA in InditexTech/foss instead of keeping a local CLA.mdPosiblemente ocupada @amagan la tomó hoy. Abiertodocumentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
InditexTech/redkey-operator#129 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Project submission: Landed MCPAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
trufflesecurity/trufflehog#5573 ·
Los mantenedores suelen responder en 1 día