continuedev / continuedev/continue

Sometimes Suggested Code by AI is not properly diffed / replaced to current source code of your working files.

Open
#12,894 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:inline-edit kind:bug
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
name: Main Config
version: 1.0.0
schema: v1
models:
  - name: Qwen2.5 Coder 32B
    provider: ollama
    model: qwen2.5-coder:32B
    apiBase: http://127.0.0.1:11434
    roles:
      - chat
      - edit
      - apply
  - name: Qwen2.5 Coder 1.5B (Autocomplete)
    provider: ollama
    model: qwen2.5-coder:7B
    apiBase: http://127.0.0.1:11434
    roles:
      - autocomplete
  - name: Qwen2.5 Coder 7B (Embeddings)
    provider: ollama
    model: qwen2.5-coder:7B
    apiBase: http://127.0.0.1:11434
    roles:
      - embed
Description

Sometimes Continue is not able to merge its suggestion to the original code.

To reproduce

I am using Qwen 2.5 32B, I am trying to work on a small C program with two C files. When I ask the LLM to do a refactoring on my code it shows the modification it needs to do and sometimes (not all the times) when I choose to "Apply" changes, his suggested code is not merged in my original C file. It says but is not able to modify the file.

Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the intermittent failure with the Continue Apply action using the provided Ollama and Qwen configuration, then trace the suggestion diff and merge flow. Done means the suggested refactoring is reliably applied to the current C file, with a regression test covering the failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, ollama, typescript
Domain
ai, developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.