Skip to content
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

[warning] could not find a pixi interpreter for the interpreter at ... #15915

Closed
p-i- opened this issue Aug 2, 2024 · 2 comments
Closed

[warning] could not find a pixi interpreter for the interpreter at ... #15915

p-i- opened this issue Aug 2, 2024 · 2 comments
Assignees
Labels
upstream-python Blocked on upstream Python Ext

Comments

@p-i-
Copy link

p-i- commented Aug 2, 2024

Type: Bug

Inspecting Output -> Python log (TRACE):

2024-08-02 15:21:20.631 [warning] could not find a pixi interpreter for the interpreter at /Users/pi/code/2024/spins/.venv/bin/python

I'm reporting this as I observed this warning while trying to solve a seemingly unrelated issue, which involves looking through the logs. And if I have three separate issues with my set up, it's difficult to prise them apart.

This particular message doesn't Google well, so if a VSCode engineer is kind enough to explain what's going on here, hopefully this issue will help future engineers in their debugging process.

Extension version: 2024.7.0
VS Code version: Code 1.92.0 (b1c0a14de1414fcdaa400695b4db1c0799bc3124, 2024-07-31T23:26:45.634Z)
OS version: Darwin arm64 23.5.0
Modes:

System Info
Item Value
CPUs Apple M2 (8 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) 24.00GB (0.69GB free)
Process Argv --crash-reporter-id f10d97cd-2115-4dba-a34a-07be9312995a
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
refactort:31108082
ccplc:31103425
pythonrstrctxt:31103193
wkspc-onlycs-c:31106320
wkspc-ranged-c:31107834

@p-i-
Copy link
Author

p-i- commented Aug 2, 2024

output-python(trace).txt

I will also cross-link the other two issues I am simultaneously trying to resolve. Although I suspect the issues are unrelated, at least this will demonstrate the difficulty an engineer faces in trying to fix a problem in VSCode.

#15914

#15911

@DonJayamanne
Copy link
Contributor

Duplicate of microsoft/vscode-python#23901 (comment)

@DonJayamanne DonJayamanne added the upstream-python Blocked on upstream Python Ext label Aug 5, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream-python Blocked on upstream Python Ext
Projects
None yet
Development

No branches or pull requests

2 participants