This topic helps you troubleshoot issues with Tanzu Developer Tools for IntelliJ.
{{> 'partials/ide-extensions/ki-cannot-view-workloads' }}
When you run or debug a launch configuration, IntelliJ deactivates the launch controls.
IntelliJ deactivates the launch controls to prevent other launch configurations from being launched at the same time. These controls are reactivated when the launch configuration is started. As such, starting multiple Tanzu debug and live update sessions is a synchronous activity.
You try to start a Tanzu Debug session and it immediately fails with an error message similar to:
Error running 'Tanzu Debug - fortune-teller-fortune-service': Unable to open debugger port (localhost:5005): java.net.ConnectException "Connection refused"
Old Tanzu Debug launch configurations sometimes appear to be corrupted after installing a later version of the plug-in. You can see whether this is the problem you are experiencing by opening the launch configuration:
- Right-click
workload.yaml
. - Click Modify Run Configuration... in the menu.
- Scroll down and expand the Before Launch section of the dialog.
- Verify that it contains the two Unknown Task entries
com.vmware.tanzu.tanzuBeforeRunPortForward
andcom.vmware.tanzu.tanzuBeforeRunWorkloadApply
.
Because these two tasks are unknown causes, these steps of the debug launch are not run. This in turn means that the target application is not deployed and accessible on the expected port, which causes an error when the debugger tries to connect to it.
It might be that although the launch configuration appears corrupt when seen in the launch config editor, in fact there is no corruption. It's suspected that this problem only occurs when you install a new version of the plug-in and start using it before first restarting IntelliJ.
There is possibly an issue in the IntelliJ platform that prevents completely or correctly initializing the plug-in when the plug-in is hot-swapped into an active session instead of loaded on startup.
Closing and restarting IntelliJ typically fixes this problem. If that doesn't work for you, delete the old corrupted launch configuration and recreate it.
{{> 'partials/ide-extensions/ki-timeout-err-live-updating' }}
On macOS, the Tanzu Panel doesn't display workloads or any other resources when using a GKE cluster. Other tools, such as the Tanzu CLI Apps plug-in, display resources correctly.
gke-cloud-auth-plugin
is required to properly authenticate to a GKE cluster.
However, when starting IntelliJ from Dock or Spotlight, environment variables set by using
.profile
, .bash_profile
, or .zshrc
are not available. For more information, see this
YouTrack issue.
This might cause gke-cloud-auth-plugin
to be missing from PATH
when launching IntelliJ and prevent
the Tanzu Panel from reaching the cluster.
Open IntelliJ from the CLI. Example command:
open /Applications/IntelliJ\ IDEA.app
On macOS, the Tanzu Panel doesn't display workloads or any other resources when setting the Kubernetes
context by using a KUBECONFIG
environment variable.
Other tools, such as the Tanzu CLI Apps plug-in, display
resources correctly.
When starting IntelliJ from Dock or Spotlight, environment variables set by using .profile
,
.bash_profile
, or .zshrc
are not available.
This causes the panels to be empty because the extension can't find the right Kubernetes context.
For more information, see this YouTrack issue.
Open IntelliJ from the CLI. For example:
open /Applications/IntelliJ\ IDEA.app
The Tanzu panel shows workloads but doesn't show Kubernetes resources in the center panel of the activity pane.
When switching the Kubernetes context, the activity pane doesn't automatically update the namespace, but the workload pane detects the new namespace. Therefore, the Tanzu panel shows workloads but doesn't show Kubernetes resources in the center panel of the activity pane.
Restart IntelliJ to properly detect the context change.
{{> 'partials/ide-extensions/ki-tnz-panel-actions-unavail' }}
{{> 'partials/ide-extensions/ki-projects-with-spaces' }}
A lock incorrectly shows that Live Update is still running and prevents Live Update from starting again.
Restarting your computer while running Live Update without terminating the Tilt process beforehand.
Delete the Tilt lock file. The default location for the file is ~/.tilt-dev/config.lock
.
An EDT Thread Exception error is logged or reported as a notification with a message similar to
"com.intellij.diagnostic.PluginException: 2007 ms to call on EDT TanzuApplyAction#update@ProjectViewPopup"
.
A UI liveness check detected something taking more time than planned on the UI thread and freezing the UI. You might experience a brief UI freeze at the same time. This happens more commonly when starting IntelliJ because some initialization processes are still running. This issue is also commonly reported by users with large projects.
If slow startup processes cause the issue, the UI freeze is likely to be brief. If a large number of files causes the issue, the UI freeze is likely to be more severe.
There is no workaround currently other than trying to reduce the number of files in your project, though that might not be practical in some cases. A fix is planned for the next release.
When an application is applied from IntelliJ it restarts frequently.
An application or environment behavior is triggering the application to restart.
Observed trigger behaviors include:
- The application itself writing logs to the file system in the application directory that Live Update is watching
- Autosave being set to a very high frequency in the IDE configuration
Prevent the trigger behavior. Example solutions include:
- Prevent 12-factor applications from writing to the file system.
- Reduce the autosave frequency to once every few minutes.