Uh oh!
There was an error while loading. Please reload this page.
Use $HOME instead of ~ in PATH env variable - #367
Use $HOME instead of ~ in PATH env variable#367Jose Blanquicet (blanquicet) wants to merge 1 commit into
Conversation
7169fa0 to
ca91064CompareDarren Tu (darrentu)
commented
Dec 6, 2023
Hi Jose Blanquicet (@blanquicet), thank you for making a PR. We will look into this and get back to you! |
Jose Blanquicet (blanquicet)
commented
Dec 6, 2023
Thanks Darren Tu (@darrentu). I haven't marked it as ready because I'm still trying to understand how to fully test it and verify that after this PR I will be able to execute binaries within |
Darren Tu (darrentu)
commented
Dec 6, 2023
The test cases are passing: https://github.com/Azure/CloudShell/actions/runs/7062144530/job/19225319429. |
Yep, but they are only testing that the |
ca91064 to
b9c28cfCompareSigned-off-by: Jose Blanquicet <josebl@microsoft.com>
b9c28cf to
2918057CompareHi Darren Tu (@darrentu), I found the issue in my previous approach. I was adding the Now the PR is ready. |
Jose Blanquicet (blanquicet)
commented
Dec 18, 2023
Hi Darren Tu (@darrentu), friendly ping to have this PR merged 🙂. Thanks! |
Hi folks,
I was running some experiments with the InnovationEngine project, which leverage the CloudShell to execute the documentation, and I faced a problem with the the
PATHenv variable. In particular, I noticed some paths withinPATHare using~instead of$HOMEand some tools don't parse~thus they aren't able to execute the binaries located on those paths. An example of the tools impacted iskubectl. Here the issue reported upstream. The solution is to use$HOMEinstead of~, which shouldn't have any impact on tools already working with~. I tried in other online shells and systems I could try, and none of them are using~withinPATH.Thanks