Sorry, no response was returned.

[vignesh7056]

Type: Bug

"Sorry, no response was returned." returned no problem with internet. this happens when we use github copilot edit feature

Extension version: 0.23.2
VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 x 1800)
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 vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	19.85GB (3.87GB free)
Process Argv	--crash-reporter-id 59e275ea-553f-41a2-af10-3d8482c01ae1
Screen Reader	no
VM	33%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyonecf:30548226
vscrp:30673768
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

[lramos15]

This a problem with Claude that we are working to improve upon. The recommendation at the moment is to try again or try another model.

[munnam77]

You just have to close and open the vs code that will solve the problem for now before they fix it permanently.

[vignesh7056]

I encountered an issue where restarting Visual Studio Code multiple times did not resolve the problem. However, after several system reboots, the issue was successfully resolved.