Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C060 Supported 2026-11-08

GitHub issue #15417 in cline/cline, opened 2026-10-28 by JoaoMarcos44, records a report verified against main commit 51f63e4fd63aeeb74d708b9c3d1f8b800aff9b3e on Windows, Node 22.16.0 and Vitest 4.0.18, that two editor calls replacing different regions of one file can both report success while one change disappears from disk, with a deterministic regression in which both calls return Edited but the final file can contain alpha new while beta stays old, and that replaceInFile and insertInFile in sdk/packages/core/src/extensions/tools/executors/editor.ts perform separate asynchronous read and full-file write operations with no coordination between editor executor instances.

Verbatim Excerpts from Cited Records
“Two `editor` calls that replace different regions of one file can both report success while one change disappears from disk. The built-in tool description explicitly recommends submitting non-overlapping edits together.”
— JoaoMarcos44 · cline/cline (issue 15417 opening body, What happens section) · 2026-10-28T23:56:32Z ·GitHub Issue ↗
“Verified against main commit `51f63e4fd63aeeb74d708b9c3d1f8b800aff9b3e` on Windows, Node 22.16.0 and Vitest 4.0.18.”
— JoaoMarcos44 · cline/cline (issue 15417 opening body, Reproduction section) · 2026-10-28T23:56:32Z ·GitHub Issue ↗
“A deterministic regression uses the actual executor and filesystem writes. It controls read completion so both operations read the original contents. Vitest runs 14 tests, with the new regression failing and all 13 existing tests passing.”
— JoaoMarcos44 · cline/cline (issue 15417 opening body, Reproduction section) · 2026-10-28T23:56:32Z ·GitHub Issue ↗
“`replaceInFile` and `insertInFile` in `sdk/packages/core/src/extensions/tools/executors/editor.ts` perform separate asynchronous read and full-file write operations. Concurrent calls can read the same snapshot and overwrite each other's results. There is no coordination between editor executor instances either.”
— JoaoMarcos44 · cline/cline (issue 15417 opening body, Cause and impact section) · 2026-10-28T23:56:32Z ·GitHub Issue ↗
Counter-record: Issue remains open as of 2026-11-07; both comments read (2 of 2 listed): the linear-code bot linkback to CLINE-3703 and a 2026-11-07 comment by DrPei12 adding a source-review edge case, two concurrent creates of a file that does not exist yet through separate executor instances with different path spellings for the same destination, noting the lock would need to cover the existence check and operation selection with the key derived from the resolved path, and stating these are source-review suggestions, not additional reproduced failures. No maintainer response, fix, or reproduction dispute appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If issue 15417 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.