G
YouTube TikTok Games
Skip to content

java-debug plugin download not validated — truncated jar silently disables debugging #324

Open

Description

@sisyphusend

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.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.

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.

Activity

  1. tartarughina commented on Nov 4, 2026

    @tartarughina
    Collaborator

    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.

  2. MrSubidubi commented on Nov 6, 2026

    @MrSubidubi
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions