You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
java-debug plugin download not validated — truncated jar silently disables debugging #324
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.
The downloaded debugger/com.microsoft.java.debug.plugin-0.53.2.jar was 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.
Could you share the logs of the failed extraction?
If those are visible from the proxy, we have a way to create a pop-up notifying the user.
If the visibility is only at the extension level we might have to find a more appropriate way.
@MrSubidubi to confirm the improvements on HTTP downloads and to share an opinion on notifying the users on failed bundle extractions.
This should have improved and I think prompting is fine, although I am not 100% sure we would currently catch all of the interrupted downloads on Zeds side. At the same time, we should now be able to more easily do just that given the refactor.
Activity
tartarughina commentedon Nov 4, 2026
For what concerns downloads we should expect to see improvements from zed-industries/zed#66048. The PR is part of the newest preview version https://github.com/zed-industries/zed/releases#release-v1.28.0-pre.
Could you share the logs of the failed extraction?
If those are visible from the proxy, we have a way to create a pop-up notifying the user.
If the visibility is only at the extension level we might have to find a more appropriate way.
@MrSubidubi to confirm the improvements on HTTP downloads and to share an opinion on notifying the users on failed bundle extractions.
MrSubidubi commentedon Nov 6, 2026
This should have improved and I think prompting is fine, although I am not 100% sure we would currently catch all of the interrupted downloads on Zeds side. At the same time, we should now be able to more easily do just that given the refactor.