Troubleshooting: Codewind for VS Code
You can also post questions on our Mattermost channel.
Codewind output stream
The Codewind output stream is available in the VS Code editor. It logs
cwctl commands together with their ouput.
Check the Codewind output stream first when troubleshooting because it is particularly useful in helping you to debug unusual problems especially when starting Codewind. Some errors will also provide you with a button to open the Codewind output stream, for example:
Finding the extension logs
If you report an issue, you will be asked to upload your logs.
- In VS Code, open Help > Toggle Developer Tools.
- Go to the Console tab.
- Enter codewind.log in the Filter box:
- Upload the contents of the log file with your issue report.
Build succeeded, but project is stuck in the Stopped state
If your project fails to start, check the application logs for anything that might indicate the failure. If your application does not have problems, you can check the Codewind logs. If the error persists, you can reset the project by disabling and re-enabling the project.
No ESLint warnings or errors for Node.js projects
Install the ESLint extension and follow the instructions to activate the extension.
Liberty project remains in the Starting - Debug state
Liberty servers started in Debug mode do not start until the debugger attaches. Run the attach debugger command, and the server starts. You can check the application logs to see if the server is starting.
Debugger attach fails with the message “Configured debug type “java” is not supported”
Install and enable the Java Extension Pack.
Debugger fails to attach after restarting project into Debug mode
Run the attach debugger command again. If the issue persists after a few attempts, restart the project in Debug mode a second time.