JetBrain Rider Continue plugin does not work

[akaspeh1]

Before submitting your bug report

• [x] I believe this is a bug. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that reports the same bug
• [X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Win 11
- Continue: com.github.continuedev.continueintellijextension (0.0.27)
JetBrains Rider 2023.3.2
Build #RD-233.13135.100, built on December 19, 2023
Runtime version: 17.0.9+7-b1087.9 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
.NET Core v7.0.10 x64 (Server GC)
GC: G1 Young Generation, G1 Old Generation
Memory: 10000M
Cores: 32
Registry:
  editor.config.csharp.support=true
Non-Bundled Plugins:
  com.github.continuedev.continueintellijextension (0.0.27)
  zielu.gittoolbox (500.1.4+222)

Description

Continue tab is displaying just raw HTML. Does not work. No logs to be found. Even when triggered trough Actions this opens

To reproduce

No response

Log output

No response

[sestinj]

@akaspeh1 Thanks for the report, and sorry you're seeing such an egregious bug. It's something I'd seen before, but was solved for the previous person with this line of code. I've unfortunately not had any luck reproducing now, even trying on Windows 11 with Rider. I'm wondering whether this same error happens in any other JetBrains IDEs, or if it is specific to Rider?

[jsco2t]

Having the exact same issue. Installed in Both intellij and goland. Both of which are running 2023.3.3. My OS is macOS 14.1.2

[jsco2t]

I'm happy to try to provide more info if needed. I was really looking forward to trying this out.

[jost]

Same problem here, seen on current versions (2023.3.3, 2023.3.4) of webstorm and rubymine on macOS. Also the settings panel is blank. No errors in idea.log. I've tried the tools with jetbrains' "New UI" as well as "Classic UI", same result for both.

[JustusSchwan]

Same problem with CLion and PyCharm on Debian 12.

Edit: I had an old version of continue installed, the most recent 0.0.33 does not throw exceptions. The error still persists, though.

[sestinj]

Thanks everyone for adding details here. Going to take another crack at this. I was excited to see that everyone is on 2023.3.3, but today someone had the same issue with a 2024 version, and I tried 2023.3.3 myself without problem

Any additional information that seems relevant may be helpful. I'll share soon if I have any updates