Skip to content

Preparing to fetch Python environment information never ends #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rebornix opened this issue Apr 28, 2025 · 3 comments
Open

Preparing to fetch Python environment information never ends #358

rebornix opened this issue Apr 28, 2025 · 3 comments
Assignees

Comments

@rebornix
Copy link
Member

rebornix commented Apr 28, 2025

Type: Bug

While using the environment tool in Copilot agent mode, Preparing to fetch Python environment information step spins forever.

2025-04-28 22:24:21.044 [info] Running: /workspaces/python-ds/venv/bin/python -m pip list
2025-04-28 22:25:40.207 [info] Terminal is activated: /workspaces/python-ds/venv/bin/python

Extension version: 0.3.11181009
VS Code version: Code - Insiders 1.100.0-insider (Universal) (c456afbf30ea22be07e2ec867db6c024ca7748ca, 2025-04-28T11:20:01.206Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux arm64 6.12.5-linuxkit

System Info
Item Value
CPUs Apple M3 Max (14 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) 5, 4, 3
Memory (System) 36.00GB (0.10GB free)
Process Argv --enable-proposed-api rebornix.anyllm --enable-proposed-api rebornix.lulu --crash-reporter-id 1ce5da70-91d5-46fb-a706-70ff08933f9c
Screen Reader no
VM 0%
Item Value
Remote Dev Container: Python 3 @ desktop-linux
OS Linux arm64 6.12.5-linuxkit
CPUs unknown (14 x 0)
Memory (System) 7.65GB (3.93GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551:31249597
vscod805:30301674
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
dwnewjupyter:31046869
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
dwcopilot:31158714
c3hdf307:31184662
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
g012b348:31231168
cp15370_c:31280196
pythoneinst12:31251391
treesitterini:31278752
bgtreat:31252123
c7cif404:31294349
31787653:31262186
3e8i5726:31271747
pythonpulldiag:31287486
6gi0g917:31259950
editoredits36407:31282444
996jf627:31264550
pythonrdcb7:31268811
usemplatestapi:31292913
i53e4855:31295464
747dc170:31275146
pythoncompactctx:31296835
aj496949:31278748
9hi5e907:31296557
pylancecolor:31288664
generatesymbolt:31280541
convertfstringf:31280702
gendocf:31280703
9e7b5698:31285110
pylancequickfixt:31296868

@rebornix
Copy link
Member Author

It used an environment that's already gone/deleted. It's likely a cache issue.

@eleanorjboyd
Copy link
Member

@karthiknadig should I be triggering a reload or anything when getting the environment? I am seeing that I get the environment from the API and it returns the deleted one and I would expect the API to fetch the up to date information here?

Image

@karthiknadig
Copy link
Member

There was a bug here that I fixed in a build that got pushed about an hour ago. Try with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants