All of a sudden, the debuggger stops at return ma.invoke(obj, args);in the java.lang.reflect.Method.class file.
And it ignores my own breakpoints.
I'm under release:
Version: 1.36.1
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:55:08.091Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-050000-generic snap
I have the following extensions:
Name: Java Extension Pack
Id: vscjava.vscode-java-pack
Description: Popular extensions for Java development and more.
Version: 0.7.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack
Name: Language Support for Java(TM) by Red Hat
Id: redhat.java
Description: Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more...
Version: 0.47.0
Publisher: Red Hat
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=redhat.java
Name: Debugger for Java
Id: vscjava.vscode-java-debug
Description: A lightweight Java debugger for Visual Studio Code
Version: 0.20.0
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-debug
Doing a Java: Clean the Java language server workspace solved the issue.
Related
I've installed the ARM version of VSCode V1.67.2 on my iMac M1 (see below). However I can't seem to get many extensions to work.
For example, I install 'pico-go' and then issue the command 'Pico-Go > Configure Project' and immediately get:
"Command 'Pico-Go . Configure project' resulted in an error (command 'picogo.initialise' not found)"
Same basic error with the Pymakr extension and many other extensions.
(On the other hand Espressif and PlatformIO seem to work!)
This seems to be a fundamental issue with my installation rather than an extension-specific issue so any assistance would be appreciated.
Susan
Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:20:04.972Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin arm64 21.5.0
I have a weird behavior with the '3' key of my MB Air keyboard in VS Code in Ruby and Elixir files only: instead of '3' it displays '#' character.
I've already looked and checked everywhere in the settings, - nothing.
In all other file extensions it works as needed (JSON, YALM, Java, etc.) but miserably fails in *.rb and *.exs files.
VS Code version:
Version: 1.65.1 (Universal)
Commit: 8908a9ca0f221f36507231afb39d2d8d1e182702
Date: 2022-03-08T02:20:11.670Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 21.3.0
I have probably around 25 odds extensions installed on my VSCode.
However some of my extensions are disabled - they seems to change a bit every time I start the VSCode and there is no option to enable it.
The only work around I have at the moment is to uninstall and install again to get it enabled.
I don't see any pattern. Why is this the case?
VSCode version:
Version: 1.47.3 (system setup)
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19042
Though not obvious to end users like you, each extension releases has a minimal VSCode version required.
For example, the Microsoft C/C++ extension showed in your screen shot is of version 1.5.1, which depends on VSCode 1.53.0 and above,
"engines": {
"vscode": "^1.53.0"
},
https://github.com/microsoft/vscode-cpptools/blob/1.5.1/Extension/package.json#L14
Since you are using a much older version (1.47.3), this extension can only be disabled to avoid conflicts.
Recently I started to get this error when starting a new VS Code window:
Cannot activate the 'Test Explorer UI' extension because it depends on the 'Test Adapter Converter' extension, which is not loaded. Would you like to reload the window to load the extension?
When I click "reload" it loads the window and the same error appears.
Any help to resolve it is appreciated.
More details on my configuration:
vs code: Version: 1.57.1 (Universal)
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:28:32.912Z (1 mo ago)
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 20.5.0
Test Adapter Converter extension v0.0.13
Test Explorer UI extension v2.20.4
PS: I also installed another extensions called Jest Runner and Jest Test Explorer.
you can separately install the extension from Test Adapter Converter!
Using version listed below. Have the experimental feature turned on, Debug button was there on the toolbar at 1 time now it's gone? Is anyone else using this feature yet?
"jupyter.experimental.debugging": true,
Version: 1.59.0-insider (user setup)
Commit: 50b3811fdc5b5c80ca516a2edfffedcbd464b033
Date: 2021-07-15T05:13:58.348Z
Electron: 13.1.6
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Windows_NT x64 10.0.19043
I had the same problem. I played a bit around and found out that ipykernel in version 6.2 or higher is necessary to get debugging running. I only had version 5.3.8 installed. Also I was a bit confused, because there is no debug symbol. The feature is called "Run by line". You can also have a lock at:
https://github.com/microsoft/vscode-jupyter/wiki/Setting-Up-Run-by-Line-and-Debugging-for-Notebooks
https://code.visualstudio.com/docs/python/jupyter-support-py#_debug-a-jupyter-notebook
As a workaround I exported my notebook to a python skript. There debugging was working as usual.