GoLand 2024.3
Build #GO-243.21565.208, built on November 13, 2024
Licensed to Michael Henderson
Subscription is active until January 31, 2025.
Runtime version: 21.0.5+8-b631.16 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 14.6.1
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 16000M
Cores: 10
Metal Rendering is ON
Registry:
ide.completion.variant.limit=500
suggest.all.run.configurations.from.context=true
ide.experimental.ui=true
i18n.locale=
terminal.new.ui=true
Non-Bundled Plugins:
org.asciidoctor.intellij.asciidoc (0.43.3)
com.sourcegraph.jetbrains (7.1.0)
com.intellij.tailwindcss (243.21565.135)
Bug Description
I have to run the “repair IDE” command much more frequently when I’m using Cody with Golang 2024.3. This has happened with every version of the plugin and older versions of the IDE; it doesn’t seem to be more or less frequent with v7.1.0 of the plugin or this version of the IDE.
From my point of view, I’ll start seeing functions reporting as “unresolved references,” even though they are, in fact, defined in the same project.
The code will compile and run; the IDE will show the tooltip docs for the function. When I repair the IDE (drop and rebuild indexes and caches), the red highlighting goes away. For a while, at least.
The errors eventually make coding irksome - autocomplete starts hallucinating, I can’t navigate, types aren’t inferred, etc.
I suspect this is caused by Cody because when I disable Cody, this doesn’t happen. I’m able to work for hours without having to repair the IDE. I enable Cody, and issues pop up within an hour.
linear[bot]
commented
1 week ago
IDE Information
GoLand 2024.3 Build #GO-243.21565.208, built on November 13, 2024 Licensed to Michael Henderson Subscription is active until January 31, 2025. Runtime version: 21.0.5+8-b631.16 aarch64 (JCEF 122.1.9) VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Toolkit: sun.lwawt.macosx.LWCToolkit macOS 14.6.1 GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation Memory: 16000M Cores: 10 Metal Rendering is ON Registry: ide.completion.variant.limit=500 suggest.all.run.configurations.from.context=true ide.experimental.ui=true i18n.locale= terminal.new.ui=true Non-Bundled Plugins: org.asciidoctor.intellij.asciidoc (0.43.3) com.sourcegraph.jetbrains (7.1.0) com.intellij.tailwindcss (243.21565.135)
Bug Description
I have to run the “repair IDE” command much more frequently when I’m using Cody with Golang 2024.3. This has happened with every version of the plugin and older versions of the IDE; it doesn’t seem to be more or less frequent with v7.1.0 of the plugin or this version of the IDE.
From my point of view, I’ll start seeing functions reporting as “unresolved references,” even though they are, in fact, defined in the same project.
The code will compile and run; the IDE will show the tooltip docs for the function. When I repair the IDE (drop and rebuild indexes and caches), the red highlighting goes away. For a while, at least.
The errors eventually make coding irksome - autocomplete starts hallucinating, I can’t navigate, types aren’t inferred, etc.
I suspect this is caused by Cody because when I disable Cody, this doesn’t happen. I’m able to work for hours without having to repair the IDE. I enable Cody, and issues pop up within an hour.
Additional context
No response