A lot of bugs recently on the chat features code apply

[davidliudev]

Before submitting your bug report

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

Relevant environment info

- OS: macOS 15.0 (24A335)
- Continue version: 0.9.228
- IDE version: Version: 1.95.2 (Universal)
- Model: claude sonnet 3.5

Description

Sometimes the chat never capture any file context

and the apply button won't work

Sometimes chat does captures the correct file, but apply to the wrong folder - (on project root, not the appropriate file)

This happens more often when the requirement is long with many context files.

To reproduce

No response

Log output

No response

[StephaneBonilla]

Same issue. In the latest version, context have stopped working. If you write the '@' in the chat, nothing happens. No way to insert any kind of context. Very anoying issue. I switched to previous version and all works fine. Hope they fix it soon.

[davidliudev]

Same issue. In the latest version, context have stopped working. If you write the '@' in the chat, nothing happens. No way to insert any kind of context. Very anoying issue. I switched to previous version and all works fine. Hope they fix it soon.

Yes. I figured that the @ won't work specifically for newly added files. Will have to restart the vs code for it to capture the new files, which is kind of annoying.

[Patrick-Erichsen]

Hi all, thanks for the heads up - there's a few different issues:

• "apply button won't work" - just opened a fix for this, will be out in new pre-release by EOD (bugfix: get codeblocks for pretoolbar #2909)
• "If you write the '@' in the chat, nothing happens." - @StephaneBonilla I'm unable to repro this locally, could you share your OS/IDE (e.g. JetBrains or VS Code)
• "@ won't work specifically for newly added files - this is a known bug, appreciate the +1, and in the meantime instead of restarting VS Code you can go to the "More" page and manually re-index
  

[StephaneBonilla]

Mode info:

VsCode version: 1.95.2 (user setup)
Commit: e8653663e8840adaf45af01eab5c627a5af81807
Date: 2024-11-07T11:07:22.054Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

Screen capture of the issue

With the version v0.8.55 all context works fine:

With v.0.8.56 context is broken:

[StephaneBonilla]

clicking "more" and "re-index" worked. Thanks.
Hope this bug get fixed.
Good job.

[rmalveis]

Mode info:

VsCode version: 1.95.2 (user setup) Commit: e8653663e8840adaf45af01eab5c627a5af81807 Date: 2024-11-07T11:07:22.054Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.22631

Screen capture of the issue

With the version v0.8.55 all context works fine:

With v.0.8.56 context is broken:

Hi Guys! I can confirm this bug in IntelliJ as well. Reindexing the codebase made @ to work again.

Intellij details:
IntelliJ IDEA 2024.3 (Ultimate Edition)
Build #IU-243.21565.193, built on November 12, 2024
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 15.1

Continue version 0.0.81 recently updated.

Before Re-index:

After Re-index:

[davidliudev]

The latest pre-release seems to still got all the path wrong for all files. When click apply, instead of applying to the existing code, it create a new file in my project root folder....

[Patrick-Erichsen]

@davidliudev - this is helpful, we recently updated the apply to create files if they don't exist but it sounds like there is a bug with pathing. Will be taking a look at this next week.

@StephaneBonilla @rmalveis - I haven't been able to reproduce this, strange that a reindex solves the issue though. You should be able to use context providers regardless of the state of your index.

Has it been persistent for either of you, or did the single reindex solve it permanently?

[Cheizr]

@davidliudev - this is helpful, we recently updated the apply to create files if they don't exist but it sounds like there is a bug with pathing. Will be taking a look at this next week.

@StephaneBonilla @rmalveis - I haven't been able to reproduce this, strange that a reindex solves the issue though. You should be able to use context providers regardless of the state of your index.

Has it been persistent for either of you, or did the single reindex solve it permanently?

I confirm that Re-indexing solves the context issue using @ for me.

[rmalveis]

@davidliudev - this is helpful, we recently updated the apply to create files if they don't exist but it sounds like there is a bug with pathing. Will be taking a look at this next week.

@StephaneBonilla @rmalveis - I haven't been able to reproduce this, strange that a reindex solves the issue though. You should be able to use context providers regardless of the state of your index.

Has it been persistent for either of you, or did the single reindex solve it permanently?

@Patrick-Erichsen Thank you for looking at it. I've made some new tests. Same installation as reported before.Regardless of which project I open, after the plugin update, I have to re-index its codebase. If I open Project X, reindex, close, reopen same project, I'll have to reindex again to have context working properly.

I'm no sure if there is a connection between the issues, but after the latest update I started to notice a warning about unknown parameter in my ollama server. However ollama was also updated so I can't say it is on Continue's side.

[Patrick-Erichsen]

I'm not certain that the issue is related to your Ollama config because we've had a lot of other users reporting this same issue.

For folks following along, the issue of not being able to use @ to select context providers in the latest release has been confirmed by multiple other users, going to follow up in this main thread: #2990