You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Python env tool (pet) does not launch due to missing execute permissions #25500
Doing a 'ls -al' shows that the execute permission is missing:
-rw-r--r--. 1 geraldtgl geraldtgl 15874240 Oct 2 12:49 ms-python.python-2025.14.0-linux-x64/python-env-tools/bin/pet
Doing a 'chmod +x ms-python.python-2025.14.0-linux-x64/python-env-tools/bin/pet' fixes the problem.
Karthik Nadig (@karthiknadig) it should have the correct permissions when we create it right? What user permissions do we check and setup the executable using?
There's nothing that needs to happen on PET side, PET will only create the executable.
Setting permissions (if required) needs to be done by Python (or other extensions) that distribute PET
chmod +x ./python-env-tools/bin/pet*
Also changing permissions in builds is not going to work, as these permissions are applicable ONLY for the machine on which chmod was executed on.
Feels like something else is going on, else every user should be running into this issue.
hm its a good point. GeraldTgl are you on a remote machine with stricter settings or maybe a enterprise managed machine? Worth determining what about your setup would cause this problem to arise for only you
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Apologies for the delay. This happened on RHEL 8 VMs that are enterprise managed through Puppet. Multiple users reported this issue and I was able to reproduce it at the time. In the mean time I do not work for this customer anymore and don't have access to their systems.
Activity
eleanorjboyd commentedon Oct 3, 2025
Karthik Nadig (@karthiknadig) it should have the correct permissions when we create it right? What user permissions do we check and setup the executable using?
GeraldTgl commentedon Oct 6, 2025
I would expect the execute permission is added during build looking at the following lines but somehow it seems this step is not running anymore?
vscode-python/build/azure-pipeline.stable.yml
Line 141 in 9cb5ae7
vscode-python/build/azure-pipeline.pre-release.yml
Line 147 in 9cb5ae7
eleanorjboyd commentedon Dec 12, 2025
Don Jayamanne (@DonJayamanne) do you know if this is something on the PET side?
DonJayamanne commentedon Jan 5, 2026
There's nothing that needs to happen on PET side, PET will only create the executable.
Setting permissions (if required) needs to be done by Python (or other extensions) that distribute PET
Also changing permissions in builds is not going to work, as these permissions are applicable ONLY for the machine on which
chmodwas executed on.Feels like something else is going on, else every user should be running into this issue.
eleanorjboyd commentedon Jan 5, 2026
hm its a good point. GeraldTgl are you on a remote machine with stricter settings or maybe a enterprise managed machine? Worth determining what about your setup would cause this problem to arise for only you
github-actions commentedon Feb 5, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
GeraldTgl commentedon Feb 5, 2026
Apologies for the delay. This happened on RHEL 8 VMs that are enterprise managed through Puppet. Multiple users reported this issue and I was able to reproduce it at the time. In the mean time I do not work for this customer anymore and don't have access to their systems.