Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

225
Visualizações
VS Code Logpoint suspends/breaks the execution unexpectedly

I am quite new to JavaScript/TypeScript development in VS Code. I wanted to start experimenting with Eclipse Theia, and so I have implemented a backend service. I wanted to put a logpoint in my backend service to see on the console when it is called.

Logpoint in VS Code

But sadly, when the execution reaches the respective line, execution is suspended. Only after resuming execution, the expected log message is printed.

This is my setup:

I have created https://github.com/xpomul/theia-boilerplate and there, a branch named hello-world.

I use VS Code 1.63.2 and the Remote Containers Extension.

Here’s what I do:

  • Start VS Code
  • Use "Remote-Containers: Clone Repository in Container Volume...“ and clone the https://github.com/xpomul/theia-boilerplate repository branch hello-world
  • After some waiting to get everything installed, open hello-world-impl.ts and add a logpoint with the expression test in line 7 (so it has a diamond symbol)
  • Do to the Run/Debug view and select the Launch Backend launch configuration and start it
  • Open a browser at http://127.0.0.1:3000 and run Edit > Say Hello

I’d expect that the backend continues running and just prints test to the log.

Instead, it breaks/suspends execution at the line of the logpoint and I need to explicitly resume.

What am I doing wrong? Is it some configuration issue? Or is the logpoint functionality dependent on the node version (Theia uses Node 12...) and is just not yet supported? Or is it because of TypeScript or the usage of inversify?

EDIT: I have also captured and attached a debug trace file, if that helps: https://dav.winklerweb.net/s/y5snhRgfiyaEF2B

about 4 years ago · Juan Pablo Isaza
1 Respostas
Responde à pergunta

0

Turns out it was a bug in vscode-js-debug:

https://github.com/microsoft/vscode-js-debug/issues/1191

It’s fixed in the latest nightly build and should be available in the next official VS Code release.

about 4 years ago · Juan Pablo Isaza Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda