Derived census pilot side depends on the JVM for declared pilot-nondeterministic cells

オープン
#2,224 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
40/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go, java
領域
tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.done
  • server::deliver_source_event = deliver_message.start
  • consumer::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.

主要言語
Go
スター
59
フォーク
20
平均マージ
10時間 23分
マージ済み PR(30日)
897

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Open-MBEE/OpenSysML のほかの issue

Open-MBEE/OpenSysML の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。