1.58.0 is missing linux-x64 and win32-arm64 builds on Open VSX
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- github-actions, java, typescript
調査の方向性
Start by reading .github/workflows/release.yml and the ovsx publish loop described in the issue, then compare its behavior with the successful Marketplace publishing step and the listed pre-releases. Confirm why Open VSX omitted the linux-x64 and win32-arm64 targets and identify a safe way to publish them; done means 1.58.0 exposes all seven expected targets or the issue documents why that release cannot be repaired.
索引モデルが issue の本文から書いたものです。
説明
On Open VSX, release 1.58.0 is published without the linux-x64 and
win32-arm64 target platforms. The same release has all seven targets on the
VS Code Marketplace.
Since the platform-specific builds are the ones that embed a JRE, a linux-x64
client falls back to the universal build, which embeds nothing. Combined with
the JDK 25 minimum introduced in 1.57.0, any Open VSX-based editor on linux-x64
without a system JDK 25+ now fails to start the language server:
Java 25 or more recent is required to run the Java extension. Please download
and install a recent JDK. You can still compile your projects with older JDKs
by configuring ['java.configuration.runtimes']
To Reproduce
- On a linux-x64 machine with only a JDK older than 25 installed, install
redhat.javafrom Open VSX (VSCodium, Theia, or any Open VSX-based editor)
on the stable channel. - The gallery resolves 1.58.0 and installs the
universaltarget, because no
linux-x64target is published for that version. - Open any Java file. The language server does not start and the Java 25
notification appears.
Target platforms published per version, from
https://open-vsx.org/api/redhat/java/<version> compared against the
Marketplace extensionquery API:
version Open VSX MS Marketplace
----------------------- -------------------------- --------------------------
1.55.0 7 targets, incl linux-x64 7 targets, incl linux-x64
1.56.0 7 targets, incl linux-x64 7 targets, incl linux-x64
1.57.0 7 targets, incl linux-x64 7 targets, incl linux-x64
1.58.0 5 targets, NO linux-x64 7 targets, incl linux-x64
1.58.2026101608 (pre) 7 targets, incl linux-x64 7 targets, incl linux-x64
1.59.2026102008 (pre) 7 targets, incl linux-x64 7 targets, incl linux-x64
Missing from Open VSX for 1.58.0: linux-x64 and win32-arm64.
Expected behavior
1.58.0 on Open VSX carries the same seven targets as the Marketplace, so
linux-x64 clients receive the platform build with its embedded JRE 25.
Environment
- Operating System: Amazon Linux 2023 (x86_64) under WSL2
- JDK version: Corretto 21.0.12.1 (the distro's repo snapshot carries no JDK 25)
- Visual Studio Code version: Open VSX-based editor, remote/WSL server
- Java extension version: 1.58.0,
universaltarget, installed from Open VSX
Additional Information
The artifacts were built correctly -- the same release published all seven
targets to the Marketplace -- so this looks like the Open VSX upload of those
two not landing, rather than a packaging problem.
The publish step in .github/workflows/release.yml loops one ovsx publish
per artifact:
for platformVsix in java-*-*-${GITHUB_RUN_NUMBER}.vsix; do
ovsx publish --skip-duplicate -p ${{ secrets.OVSX_MARKETPLACE_TOKEN }} --packagePath ${platformVsix}
done
In glob order the outcome was: darwin-arm64 ok, darwin-x64 ok,
linux-arm64 ok, linux-x64 missing, win32-arm64 missing,
win32-x64 ok. Because run: blocks execute as bash -e, a non-zero exit
would have aborted the step before win32-x64 succeeded -- so ovsx publish
appears to have exited 0 without persisting those two uploads.
Worth noting that --skip-duplicate means a re-run will not re-upload a
version Open VSX already records, so 1.58.0 probably cannot self-heal. Either a
manual upload of the two missing targets, or a republish under a new version,
would be needed.
The pre-releases immediately before (1.58.2026101608, 16-Oct) and after
(1.59.2026102008, 20-Oct) both published all seven targets from the same
workflow, which points at a single transient failure rather than a config
change.
- 主要言語
- TypeScript
- スター
- 2.3k
- フォーク
- 550
- 平均マージ
- 5日 1時間
- マージ済み PR（30日）
- 18
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
redhat-developer/vscode-java のほかの issue
-
bug
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
redhat-developer/vscode-java#4558 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
redhat-developer/vscode-java#4550 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
redhat-developer/vscode-java#4537 ·
メンテナーはふだん 1 日以内に返信
-
bug need info
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
redhat-developer/vscode-java#4520 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
redhat-developer/vscode-java#4517 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
redhat-developer/vscode-java の issue をすべて見る
似ている issue
-
a10y a10y-audit ai-driven-qa claude
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
linagora/twake-directory-manager#219 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
type: bug
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
メンテナーはふだん 1 日以内に返信
-
0️⃣ phase/new
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installs対応中かも @zephyr91 が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
danielmiessler/LifeOS#2393 ·
メンテナーはふだん 4 日以内に返信