Add/Delete Method not implemented - Hot Code Replace

Aberta
#1,200 4 comentários 2 reações 1 responsável Ver no GitHub

@testforstephen já está trabalhando nisso.

Desde 5/8/2022.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

ai-triaged bug hcr question

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.

Linguagem predominante
TypeScript
Estrelas
591
Forks
429
Merge médio
1d 9h
PRs com merge (30d)
19

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-java-debug

Todas as issues de microsoft/vscode-java-debug

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.