Apply To ... Doesn't Work For Notebooks

by ADMIN 40 views

A Bug Report for the Copilot Extension

Bug Type

Bug

Issue Description

When creating a new .ipynb file and making a query to the Copilot ask mode, the option to 'apply to ' is available. However, the edits either don't get applied or the 'apply to' notification suggests it is stuck. This issue is reproducible with the current version of the Copilot extension (0.26.5) and VS Code (1.99.3).

System Information

Item Value
CPUs Apple M2 Pro (10 x 2400)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
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
webnn: disabled_off
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.15GB free)
Process Argv --crash-reporter-id fbfb57fd-178e-4b32-82cf-9b50cab2a96d
Screen Reader no
VM 0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31249601
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
31787653:31262186
3e8i5726:31271747
996jf627:31283433
usemplatestapi:31288272
7bj51361:31289155
747dc170:31275177
aj496949:31278748
aj953862:31281341

Logs

Logs 
Debug: [LanguageModelAccess] UPDATING language models
Trace: Resolving chat model
Trace: Resolved chat model
Debug: [LanguageModelAccess] DID UPDATE language models
Trace: Resolving embedding model
Trace: Res embedding model
Trace: Resolving embedding model
Trace: Resolved embedding model
Trace: Resolving embedding model
Trace: Resolved embedding model
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Building intent detector
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Built intent detector
Info: message 0 returned. finish reason: [stop]
Info: request done: requestId: [b9465899-3231-48db-aecb-c29d34023a35] model deployment ID: []
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Resolving chat model
Trace: Resolved chat model
Trace: [panel] chat request received from extension host
Trace: Processing intent
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Processed intent
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Built prompt
Trace: Sending prompt to model
Info: message 0 returned. finish reason: [stop]
Info: request done: requestId: [09c7d3b3-2f34-4bf6-9934-7d50e2183f11] model deployment ID: []
Trace: Resolving chat model
Trace: Resolved chat model
Trace: Resolving chat model
Trace: Resolved chat model
Info: message 0 returned. finish reason: [stop]
Info: request done: requestId: [7e4d3b8d-0f69-45b2-899d-13ef195395dd] model deployment ID: []
Info: message 0 returned. finish reason: [stop]
Info: request done: requestId: [92188359-f394-4240-8bdb-366f23b2086b] model deployment ID: []
Trace: Resolving chat model
Trace: Resolved chat model
Info: srequest done: chatRequestId: [undefined], speculationRequestId: [73edbe2c-1b3e-48ab-9ca6-bfbd3141ebaf]
Debug: [context keys] Window state change. Needs offline check: false, active: true, focused: false.
Debug: [context keys] Window state change. Needs offline check: false, active: true, focused: true.
Debug: [context keys] Window state change. Needs offline check: false, active: true, focused: false.
Debug: [context keys] Window state change. Needs offline check: false, active: true, focused: true.

Reproduction Steps

  1. Create a new .ipynb file in VS Code.
  2. Make a query to the Copilot ask mode.
  3. Select the option to 'apply to '.
  4. Observe that the edits either don't get applied or the 'apply to' notification suggests it is stuck.

Expected Behavior

The edits should be applied successfully, and the 'apply to' notification should not suggest it is stuck.

Additional Information

  • Extension version: 0.26.5
  • VS Code version: 1.99.3
  • OS version: Darwin arm64 24.4.0

Q: What is the issue with the 'apply to' feature in the Copilot extension?

A: The 'apply to' feature in the Copilot extension is not working as expected for notebooks. When you select the option to 'apply to ', the edits either don't get applied or the 'apply to' notification suggests it is stuck.

Q: What are the reproduction steps for this issue?

A: To reproduce this issue, follow these steps:

  1. Create a new .ipynb file in VS Code.
  2. Make a query to the Copilot ask mode.
  3. Select the option to 'apply to '.
  4. Observe that the edits either don't get applied or the 'apply to' notification suggests it is stuck.

Q: What are the expected behavior and outcome for the 'apply to' feature?

A: The expected behavior is that the edits should be applied successfully, and the 'apply to' notification should not suggest it is stuck.

Q: What are the system requirements for this issue to occur?

A: This issue is reproducible with the current version of the Copilot extension (0.26.5) and VS Code (1.99.3) on Darwin arm64 24.4.0.

Q: What are the possible causes of this issue?

A: The possible causes of this issue are:

  • Bug in the Copilot extension
  • Bug in the VS Code extension
  • Incompatibility between the Copilot extension and VS Code
  • Incompatibility between the Copilot extension and the notebook file format

Q: How can I report this issue to the developers?

A: You can report this issue to the developers by providing the following information:

  • A detailed description of the issue
  • The reproduction steps
  • The expected behavior and outcome
  • The system requirements
  • Any additional information that may be relevant to the issue

Q: What are the next steps for resolving this issue?

A: The next steps for resolving this issue are:

  • Investigate the issue and determine the root cause
  • Develop a fix for the issue
  • Test the fix to ensure it resolves the issue
  • Release the fix to the public

Q: How can I stay up-to-date with the progress on resolving this issue?

A: You can stay up-to-date with the progress on resolving this issue by:

  • Following the issue on the Copilot extension GitHub page
  • Subscribing to the Copilot extension newsletter
  • Joining the Copilot extension community forum

Q: What are the potential consequences of not resolving this issue?

A: The potential consequences of not resolving this issue are:

  • Users will continue to experience the issue and may become frustrated with the product
  • The issue may prevent users from using the product effectively
  • The issue may lead to a loss of business or revenue for the company

Q: What are the potential benefits of resolving this issue?

A: The potential benefits of resolving this issue are:

  • Users will be able to use the product effectively and efficiently
  • The issue will be resolved and users will no longer experience the problem
  • The company will be able to maintain a positive reputation and build trust with its customers.