Shalom Ben Zvi Kazaz

That's what I did to avoid the deprecated apt-key with debian testing: gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF gpg --export 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF >out cat out|gpg --dearmor | sudo dd of=/usr/share/keyrings/mono.gpg rm out...

releted https://github.com/digma-ai/digma-intellij-plugin/issues/2047

we decided not to merge this PR

@doppleware ctrl+c works for copy. right click or context menu doesn't work on linux for some reason and also doesn't work for some windows users. looks like it works only...

we get errors like this one java.lang.NoClassDefFoundError: org/jetbrains/kotlin/idea/stubindex/KotlinTopLevelFunctionFqnNameIndex at org.digma.intellij.plugin.idea.psi.discovery.endpoint.KtorFrameworkEndpointDiscovery.lookForRoutingBuilderEndpoints$lambda$10$lambda$3(KtorFrameworkEndpointDiscovery.kt:77) at com.intellij.openapi.project.DumbService.runReadActionInSmartMode$lambda$0(DumbService.kt:77) at com.intellij.openapi.project.DumbService.runReadActionInSmartMode$lambda$2(DumbService.kt:129) at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:909) at com.intellij.openapi.application.ReadAction.compute(ReadAction.java:65) at com.intellij.openapi.project.DumbService.runReadActionInSmartMode(DumbService.kt:122) at com.intellij.openapi.project.DumbService.runReadActionInSmartMode(DumbService.kt:77) at org.digma.intellij.plugin.common.PsiAccessUtilsKt.runInReadAccessInSmartModeWithResultAndRetryIgnorePCE$lambda$5(PsiAccessUtils.kt:65) at org.digma.intellij.plugin.common.RetryUtilsKt.runWIthRetryWithResultIgnorePCE(RetryUtils.kt:81) at org.digma.intellij.plugin.common.RetryUtilsKt.runWIthRetryWithResultIgnorePCE$default(RetryUtils.kt:70) at org.digma.intellij.plugin.common.PsiAccessUtilsKt.runInReadAccessInSmartModeWithResultAndRetryIgnorePCE(PsiAccessUtils.kt:61)...

the details are in this slack thread https://jetbrains-platform.slack.com/archives/CPL5291JP/p1686183871369739 need to check if the problem was solved in latest gradle-intellij-plugin

Update: the issue is described here https://youtrack.jetbrains.com/issue/IDEA-318263#focus=Comments-27-7274096.0-0 the problem is when using instrumentedJar as suggested by jetbrains then debugger breakpoints are opened in the class file in the instrumented jar...

duplicate of #1729

@kshmidt-digma @shaykeren

// todo: jetbrains recommend using the instrumented jar // https://plugins.jetbrains.com/docs/intellij/tools-gradle-intellij-plugin.html#multi-module-project // but there is a bug. // https://github.com/digma-ai/digma-intellij-plugin/issues/1017 // https://youtrack.jetbrains.com/issue/IDEA-318263#focus=Comments-27-7274096.0-0 // the workaround suggested in youtrack didn't work // but...