Inline chat fails with `startIndex must be less than endIndex`

[digitarald]

Type: Bug

Running an Inline Chat in an empty cell, but also affects empty files.

[error] Error: startIndex must be less than endIndex
    at new Ql (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:190:9911)
    at ATe (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:802:7291)
    at kTe (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:802:7036)
    at LTe (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:802:13862)
    at Au (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:802:24178)
    at YI.prepare (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:832:12969)
    at /Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:61:45460
    at async Promise.all (index 0)
    at Xe._processPromptPieces (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:61:45383)
    at Xe.render (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:61:46407)
    at Xe.render (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:780:2849)
    at bv.buildPrompt (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:832:20766)
    at YTe (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:847:200)
    at dp.fetchResponse (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:848:2585)
    at dp.provideInteractiveEditorResponse (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:847:2016)
    at Dc.handleCommonInlineChatRequest (/Users/digitarald/.vscode-insiders/extensions/github.copilot-chat-0.17.2024062601/dist/extension.js:882:3911)
    at g.$invokeAgent (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:154:50217)

Uses https://github.com/LadyKerr/msft-build-copilot-demo/blob/1068006c3616b8d9432949293b5b1ec390f4dd98/Flight_Data_Analysis.ipynb#L4 .

Extension version: 0.17.2024062601 VS Code version: Code - Insiders 1.91.0-insider (0354163c1c66b950b0762364f5b4cd37937b624a, 2024-06-26T10:12:33.304Z) OS version: Darwin x64 23.5.0 Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	5, 4, 4
Memory (System)	64.00GB (2.85GB free)
Process Argv	--log trace --crash-reporter-id 4cf0a6f0-aaf8-4da3-9b2b-81f6c639c12b
Screen Reader	no
VM	0%

[mp035]

I have the same issue using the copilot chat window

Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.6.40-1-MANJARO snap

[ZHHHH9980]

i wrote something a single string like 'x' instead of empty file, which fixed the problem temporarily.

[laurentfontaine1967]

Depuis le 27 Juin le problème n'est toujours pas traité par Github ! ?

[JhairSilvaOjeda]

Same issue :s

[raffaelmeier]

Here as well...

[liangyu-git]

It happens very frequently to me...

[alexdima]

This is now fixed and the fix is available in our pre-release channel (you can use VS Code Insiders + the pre-release version of the Copilot Chat extension). The fix will soon (in about 1 week) be rolled out to stable.

cc @hediet