java-debug plugin download not validated — truncated jar silently disables debugging
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
The download and install logic for the java-debug plugin jar lives in the Rust extension code of this repository, so start by locating where the debugger jar is fetched and where its presence is checked. Add a size or checksum comparison against the release asset and re-download on mismatch, and confirm the error path surfaces a bundle-load failure. Done means a truncated jar is detected and replaced on the next start, which can be checked by truncating the file manually and restarting.
Written by the indexing model from the issue text.
Description
Summary
The com.microsoft.java.debug.plugin jar is downloaded without any integrity check. A truncated file is accepted as a valid install and silently breaks all debugging.
What happened
- Extension version: 6.8.30 (WSL remote, Zed 1.26.2)
- The downloaded
debugger/com.microsoft.java.debug.plugin-0.53.2.jarwas 668,580 bytes instead of the real 3,107,682 bytes (download interrupted back in April; no validation, so the fragment was kept) - On every jdtls start, bundle loading fails (visible in jdtls
~/.cache/jdtls-*/.metadata/.log):Cannot extract bundle symbolicName or version .../com.microsoft.java.debug.plugin-0.53.2.jar - Consequently all debug delegate commands are unregistered: any debug session reports
No delegateCommandHandler for vscode.java.resolveMainClass - This state persisted for months because nothing surfaces the load failure
Fix suggestion: validate the download (size against the release / checksum) and re-download on mismatch, or at least surface bundle-load failures to the user.
Workaround that fixed it locally: re-download the jar from https://github.com/zed-industries/java-debug/releases/download/0.53.2/com.microsoft.java.debug.plugin-0.53.2.jar and fully restart Zed.
- Dominant language
- Rust
- Stars
- 225
- Forks
- 47
- Avg merge
- 3h 51m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zed-extensions/java
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
zed-extensions/java#325 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zed-extensions/java#133 · 1 comment ·
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
zed-extensions/java#323 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
zed-extensions/java#272 · 6 comments ·
-
language-server
Difficulty 4/5 3-5 days Newbie friendliness 25/100
zed-extensions/java#246 · 4 comments ·
All issues in zed-extensions/java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gitbutlerapp/gitbutler#16982 ·
Maintainers usually reply within 1 day
-
priority: high status: new topic: ga4gh-sdk type: docs type: maintenance workload: minutes
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
C-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rust-lang/rust-clippy#17976 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
aaif-goose/goose#13327 ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day