After November's Recovery Update 2, VSCode fails to start debugging on pre-saved workspaces.
It is MacOS specific. Don't know if it is M1 specific.
If I open the workspace's folders one by one and manually add them to a new workspace, debugger starts fine.
As soon as I save the workspace to a file, that's when debugger cannot start.
Has anyone experienced the same problem?
Temporary fix for anyone with the same problem: Open up your terminal and run
code /path/to/workspaceFile
Maybe is a permissions issue with the new update?
The problem is present if I do a fresh install of the VSCode.app
Related
Whenever i try save a go file inside vc code i get this pop up Failed to run '/usr/local/go/bin/go env. The config change may not be applied correctly. . Also there is any no go intelliSense, code navigation, and code editing support.
I guess, you are using go modules and have go.mod file inside project directory. In this case, inside VsCode, go to preferences. Under extensions, select Go. Untick checkbox labelled "Infer GOPATH from the workspace root." for both "User" and "Workspace".
Close all terminal and VsCode instance, and restart VsCode. It should no longer display the error, and prompt message to install Go Tools. Else you can manually install go tools from VsCode (pressing crtl/cmd + shift + P), which will bring back intellisense and linting.
In case you are using Mac OS and installed Go via homebrew add
"go.goroot": "/opt/homebrew/opt/go/libexec"
To your settings.json file. The path may be different. Check it via export GOROOT="$(brew --prefix golang)/libexec".
Also see install go on mac
I have solved this issue. The solution is that, create a new Golang project and move all the required logic files from older project to newer project and it will work. The problem is with .mod and .sum files. It is a older project that i have created on my other laptop that has Ubuntu based Feren OS. When I moved this project to my newer laptop that has Ubuntu based Zorin OS. It creates problem. So after trying lots of solution, I just created a new Golang project and moves all the required files and it works.
I'm working on setting up the Suitecloud Development Framework in the NetSuite instance for my company. I've installed Node v16.13.0, npm 8.1.0, and suitecloud 1.3.1.
Running node -v, npm -v, etc. all works from cmd but will throw a not recognized error when I use the terminal in VSCode.
I can get my VSCode to identify node with
SET PATH=C:\Program Files\Nodejs;%PATH%
but this only fixes it for the session and still doesn't give me access to run anything from suitecloud.
I've checked my Environment Variables as per every other help section I've found for this issue but I have 'C:\Program Files\nodejs' in both my user PATH variable any my system PATH variable.
I've tried running VSCode as Admin on the off chance that would fix it, but that didn't solve anything either.
Thank you for your time, hopefully I'm overlooking something simple due to my inexperience with the terminal.
Leaving VSCode overnight and then rebooting seems to have fixed it. I can't explain why, but if you're encountering the same issue I recommend walking away and coming back to it after a long delay.
After installing the Python extension, I find myself not being able to debug. When I select any of the default launch configurations and press the green arrow to start debugging, it notifies me with the error message in the title. I am not using any external modules, I am simply trying to run a single line hello world program and this error still appears. I have tried reinstalling the extension, deleting the .vscode folder and checking the path of my Python interpreter.
I had the same problem, it was gone after I delete c:\users\username\ .code and reinstall vscode. hope that helps.
Lidong
I used "renamed" function to rename a variable named "DefaultRequestURL" in Xcode 9, it alert this:
alert image
I have checked the file "ComposeController.swift", there is no "DefaultRequestURL"。
I have restart Xcode and do "Product -> Clean", it still failed.
why this? What should I do?
Try again in few minutes. Maybe background indexing still running. Also, you must build your project in order to be able to use refactor->rename.
Actually, it must be a bug in Xcode 9. Try 9.1 beta, refactor is not ideal, but works better there.
this maybe helpful: https://forums.developer.apple.com/thread/80331
UPDATE:
Close Xcode
Go to ~/Library/Developer/Xcode/DerivedData and remove folder contents including "ModuleCache".
Open your project and build
Try rename functionality now. It should work!
Update 2:
For Xcode 10, it's enough just to restart it.
Update 3:
Still works for Xcode 12. Sometimes just restart helps, sometimes module cache needs to be removed. Sometimes even build->clean helps.
Thanks for Vlad E. Borovtsov, It's help me to resolve problem and I fonud there is a way not close xcode.
This is my way to fix it:
Go to ~/Library/Developer/Xcode/ , remove DerivedData folder
command+r to run ,or command+b to build
Try rename , it work for me .
xocde reindex and rename can work
There is no need to remove DerivedData folder & rebuild.
close Xcode
remove DerivedData/ModuleCache.noindex folder
open Xcode
rename/refactor
Working on 10.2.1
Update
Working on Xcode 12 beta 4 but did need to wait for indexing to finish.
For me there was already a folder with the name I tried to rename to for some reason. Manually removing the folder helped.
I'm using Nodeclipse 0.10 with nodemon, but when I try to debug my script it doesn't stop at any of my breakpoints. I've already seen this and this answer but it hasn't helped.
Occasionally, it will stop on the first line of nodemon, other times it gives me a timeout error from the V8 VM, and sometimes it doesn't do anything at all.
Here's what I've tried so far:
I tried both the "Node application" and the "Node with monitor", neither one works.
Removed nodemon from the preferences page, but then Eclipse just complains it's missing the nodemon path and won't start my script (even if I select "Node application")
Ran node --debug-brk=5858 from the command line and then tried to attach the Eclipse debugger to it
Tried launching the debug from the toolbar button (my personal default) as well as from context menu after right clicking the script file - that just makes it stop on the module.exports line of the script
Ran eclipse --clean
None of it works. As a side note, I did not install Nodeclipse into a new Eclipse environment when I installed it, because it took me a long time to configure my existing one to where I liked it, and I'd rather be able to keep that.
Anyone dealt with this issue before?
Ok, this was embarassingly stupid...somehow, "Skip all breakpoints" had become activated in the Run menu in Eclipse. It's working now.
Thanks everyone for the help though. :)
There is already version 0.11, that has some improvements. You can try it within Enide Studio 2014. But of course, it does not matter whether it is fresh new or updated Nodeclipse version.
You should have paid attention to Nodeclipse Console messages, especially when there are question. You would what actual node command is executing. And I guess there won't be --debug-brk=5858.
Right-click on the launched file, select Properties or press Alt+Enter,
then if in Run/Debug Setting you see 2 or more Launch configuration, delete all or some. They are created automatically during first launch (with message in Nodeclipse Console)
I am currently Nodeclipse project lead, but I don't continue with nodemon support, as I am not using it. I would appreciate feedback, research and suggestion on how to improve that flow.