Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
batect.cmd broken on windows with powershell core installed
See original GitHub issueDescribe the bug
Seems to be the same issue from #627
Reinstating @thirkcircus’ original fix from #629 fixes the issue for me.
Reproduction repo
No response
Steps to reproduce
In powershell core
Run ./batect -T
Expected behaviour
Available tasks are listed
Actual behaviour
Version information
Same behavior on `0.70.1` (version from screenshot), and `0.81.1`
Any other information
No response
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
CLI reference | Batect
Windows containers always use directory mounts for caches. Example: ./batect --cache-type=directory the-task ...
Read more >Vcpkg does not find system installed Powershell Core #9606
Describe the bug If I try to install tbb (.\vcpkg.exe install tbb --triplet x64-windows), vcpkg reports that a suitable version of ...
Read more >error in all terminals visual studio 2019 - Microsoft Q&A
i get this error in the cmd: Common7\Tools\VsDevCmd.bat not found. and when i use developer powershell i get this error inside powershell:.
Read more >Server 2012 Server Core powershell not installed
Use the Deployment Image Servicing and Management (DISM.exe) tool to enable PowerShell: dism.exe /online /enable-feature /featurename: ...
Read more >Act: Run your GitHub Actions locally | Hacker News
https://batect.dev/ this is like Act but agnostic and public ... and wrap your favorite container command line tool into a working local ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oh. I had
$PSModulePath = C:\Program Files\PowerShell\7\Modulesset in user variables and removing it fixes the issue 🙌Yep! Thanks for all your help 🙏