I had this error today after updating my IntelliJ IDEA on Windows machine and trying to access project on my remote Ubuntu virtual machine over SSH with JetBrains Gateway.
JetBrains Client 2022.1
JetBrains Gateway 2022.1
IntelliJ IDEA 2022.1 (Ultimate Edition)
TL/DR
I've removed whole /home/user/.cache/JetBrains folder.
Explanation
I've resolved my problem by checking logs:
#c.i.i.StartupUtil - JVM options: [-Djava.home=/home/user/.cache/JetBrains/RemoteDev-IU/...
Line 86164: 2022-04-25 09:40:57,760 [ 288] INFO - STDOUT - This
IDE build has expired. Please download a new build from JetBrains
official site
Since it was remote project on my Ubuntu 20.04 virtual machine.
I've removed whole /home/user/.cache/JetBrains folder.
Next time I started my remote project from JetBrains Gateway it downloaded client and other missing files automatically on my Ubuntu machine and then everything worked.
For some reason IDE on Ubuntu side didn't get updated when opening remote project on Ubuntu.
Try switching your login shell on the server to bash.
Related
I am trying to connect to a remote server using JetBrains Gateway, so that I can use IntelliJ IDE for code changing purposes.
Both IntelliJ and JetBrains Gateway are -newly installed- on my device and I've rebooted my PC after installation as well.
I entered the hostname, password and it says that I'm "Successfully Connected".
But in the IDE version dropdown, nothing shows up even though I have IntelliJ installed on the system.
I do see the Other options... link. But the following options seem like they are to be used if no IDE is installed :
My Question is
How to get IntelliJ IDE (which is already installed) in the dropdown of JetBrains Gateway
You need to run a script to turn the server on
"The main script to run a remote IDE is remote-dev-server.sh, located in the bin subdirectory of your unpacked IDE"
From the Jetbrains instructions here
This has been happening ever since I have updated Intellij (IDEA CE 2020.3) to a newer version (today). I am getting this exception from the plugin when running the Develop on Kubernetes Run Configuration that I usually use with my local Minikube instance to get all of the services in the cluster up and running, and able to Debug in debug mode.
My local Minikube instance is fine shown by the following:
(Dev) $ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
I've tried checking for updates, restarting Intellij, and I am still getting the same thing. It must be something in relation to my Intellij Update but we'll have to see...
The full stack trace is:
java.util.ServiceConfigurationError: io.grpc.ManagedChannelProvider: io.grpc.netty.shaded.io.grpc.netty.NettyChannelProvider not a subtype
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1236)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1264)
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1299)
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1384)
at io.grpc.ServiceProviders.loadAll(ServiceProviders.java:67)
at io.grpc.ServiceProviders.load(ServiceProviders.java:42)
at io.grpc.ManagedChannelProvider.<clinit>(ManagedChannelProvider.java:37)
at io.grpc.ManagedChannelBuilder.forAddress(ManagedChannelBuilder.java:37)
at com.google.cloud.tools.intellij.kubernetes.skaffold.events.SkaffoldEventHandler.newManagedChannel(SkaffoldEventHandler.kt:319)
at com.google.cloud.tools.intellij.kubernetes.skaffold.events.SkaffoldEventHandler.listenEvents(SkaffoldEventHandler.kt:75)
at com.google.cloud.tools.intellij.kubernetes.skaffold.run.SkaffoldCommandLineState$startProcess$1.invokeSuspend(SkaffoldCommandLineState.kt:189)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:740)
I am getting the same behaviour in both DEBUG mode and RUN mode.
Environment Info
IDE type: IntelliJ
IDE version: Community Edition 2020.3
Cloud Code version: 20.10.1-202
Skaffold version: v1.14.0
Operating System: Windows 10 Pro 64-bit
Any help, suggestions or resolutions would be really appreciated so thank you in advance! Thanks
This issue was fixed with patch release 20.12.1 that was put out shortly after the EAP release. Please try it out and if you run into any other issues feel free to post on our GitHub. – eshaul
I am using SonarLint for Intellij 2.0, It's connected to my own SonarQube server v5.4 with no issues reported by the plugin when going into Connected Mode.
It seems not to be in sync with my server rules. Found those mentioned in the doc for Java but they also seemed not to be all. I wonder if these java rule list are used only when it's not connected to any server only.
Does it have a restriction on what rules to use or synchronize when using a remote server? Am I missing any step?
Is in any case this issue related? https://jira.sonarsource.com/browse/SLI-57
I am running:
Intellij 15.0.2 build #IU-143.1184
JRE 1.8.0_40-release-b105 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
SonarLint for Intellij 2.0
Thanks
Rules listed in SonarLint website are indeed the one enabled when you are not connected.
When you are connected the rules are the one enabled in the quality profile of the associated project.
To investigate your issue please open a thread in SonarLint Google group.
I have a TestNG setup running on Eclipse Indigo 20120216-1857 and TestNG for Eclipse v2.0. Dev environment is Mac OSX 10.8.2. Target is a web server running on Ubuntu 12.04.
Error: 'Couldn't contact the RemoteTestNG client. Make sure you don't have an older version of testng.jar on your class path.'
This error only happens when i'm running selenium scripts. not on my other api oriented test cases. I have selenium-server-standalone-2.25.0.jar running.
This same setup is working on my windows 7 dev environment.
This is a brand new eclipse setup and workspace on the mac.
I had met same question. I hope my resolved method can help you.
Method:
Please open Eclipse->Preferences->Then click TestNG->Restore Defaults
root reason: I had use ReportNG instead of testng default report,but after that I forgot to restore config. So when I make a new project,run as TestNG,but not add ReportNG jars, it report error.
I can't figure out where I am going wrong. I have Eclipse Indigo, JBoss 7.1, JBoss Tools installed. I have this configuration working on my Windows7 64-bit system. I am attempting to set up a co-worker's Windows XP 32-bit machine with the same configuration but am not able to get the server to launch. I have configured the server but when I attempt to start the server, I get an error indicating that it was unable to start the server but there is no specific error listed.
I am able to start JBoss from the command prompt using the standalone.bat file.
I am able to configure the standalone.xml file from within Eclipse. I have confirmed this by checking the file in the standalone/configuration directory.
When I attempt to publish the project from within Eclipse, it does not publish.
Nothing gets written to server.log
The startup parameters match what I have on my computer.
I can't figure out what I am missing. Any suggestions would be appreciated!
Edit:
I have done some more checking. I am able to publish to the server and I am able to start the server (with the published application) fine from the command prompt. That part works. When I attempt to start the server from within Eclipse it gives me "Server JBoss 7.1 Runtime Server failed to start." It never writes anything to the console tab in Eclipse either so I can't tell why it is failing to start.
Also in the Servers tab, there is an entry called "Server Details". When I expand that entry, it says "Not Connected".
The answer to my problem is that Eclipse had be configured to use the java JDK, not the JRE. As soon as I switched over to use the JDK it started working fine. For some reason JBoss will start under 64-bit windows with the JRE but under 32-bit you need to use the JDK. I found the answer here: https://community.jboss.org/thread/169097