microsoft / microsoft/vscode-java-debug

Add/Delete Method not implemented - Hot Code Replace

Offen
#1,200 4 Kommentare 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@testforstephen arbeitet bereits daran.

Seit 05.8.2022.

ai-triaged bug hcr question
Vorherrschende Sprache
TypeScript
Sterne
591
Forks
429
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
19

Beschreibung

My company works on a larger sized Java project, and we cannot get hot code replace to work in vscode. I suspect this is probably related to something about our specific project and how it's set up, and I'm hoping someone can give further direction for troubleshooting the problem.

Environment
  • Operating System:
    • Host: Ubuntu 22.04/21.10
    • Running App (Docker Images):
      • FROM ghcr.io/graalvm/graalvm-ce:java17-21.3.0
      • FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:18-bullseye (installing graal manually)
  • JDK version: 17 (graal, but also tested using open-jdk)
  • Visual Studio Code version: 1.69.2
  • Java extension version: 1.9.0 (Redhat)
  • Java Debugger extension version: 0.43.0
Steps To Reproduce

Due to the complex nature of our project, I'm not sure how to provide a reproducible example. Here are some things we've tried.

  • We run our java app in a container managed by kubernetes. We are able to attach the debugger to the running process, but hot code deploy will fail to work.
  • We've recently ported our app into a vscode dev container, attached to that local running process, and unsuccessfully done hot code deploy

We came from using NetBeans where this worked flawlessly, and just confirmed it still works. I've also confirmed Intelij can successfully do hot code deploy as well with our project.

Current Result

Our most simple test is adding a system.out to an existing method. No other changes. That produces the following stacktrace.

image

Other Information

We've reviewed the information at here and here with no luck.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.