You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step to Reproduce:
For me, all I have to do is click on the debug Test on a unit test. It begins compiling and then fails. I see the following message
void org.eclipse.jdi.internal.connect.ConnectionImpl$StringArgumentImpl.(org.eclipse.jdi.internal.connect.ConnectorImpl, java.lang.String, java.lang.String, java.lang.String, boolean)
(This is NOT project dependent)
This worked fine yesterday. Nothing was updated, nothing was touched that I am aware of.
Expected Behavior:
I would expect it to run the test and allow a break point to be set and work
Carl Bartlett (@vbbartlett) VS Code is now at 1.57.1 and we always recommend using the newest version. And the fix is only available with a newer version of extensions. Are you able to upgrade now?
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.
Activity
testforstephen commentedon May 1, 2021
We released a hotfix release 0.33.1 for debugger. It fixed the issue that cannot debug unit test. Could you try it?
Also "Debugger for Java" 0.33.1 requires a minimum VS Code 1.55 to install it.
vbbartlett commentedon May 3, 2021
No because I am on Centos 7 and 1.53>= don't work. other suggestions?
jdneo commentedon May 7, 2021
Carl Bartlett (@vbbartlett) Please update the VS Code to >= 1.55 and then update the
Debugger for Javato0.33.1vbbartlett commentedon May 7, 2021
Sheng Chen (@jdneo) Did you not read? 1.55 crashes on Centos 7 so I can't upgrade...
akaroml commentedon Jun 23, 2021
Carl Bartlett (@vbbartlett) VS Code is now at 1.57.1 and we always recommend using the newest version. And the fix is only available with a newer version of extensions. Are you able to upgrade now?
vbbartlett commentedon Jun 23, 2021
Rome Li (@akaroml) - no VS Code dropped support for Centos 7 at version 1.52.1. And I can not change the operating system as it is corporate mandated.
jdneo commentedon Jul 21, 2021
Then the workaround has to be:
extensions.autoUpdatetoNonetemporarilyBut remember to update all the extension & VS Code to latest once it's possible
jdneo commentedon Feb 18, 2022
According to https://stackoverflow.com/a/66660846/13068918
Start from 1.60.0, VS Code should be able to run on CentOS 7. Carl Bartlett (@vbbartlett) Maybe you can have a try.
no-response commentedon Mar 4, 2022
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.