Open asyba opened 4 years ago
The error indicates that it longer than 5 seconds to run
sam --version
Do you happen to have any kind of virus/file scanning software running on your machine? Can you run a
time sam --version
from a terminal?
Upgrading to sam cli stable 0.44.0, it fixed. You should update the documentation to required a newer version.
time sam --version SAM CLI, version 0.44.0 sam --version 0,44s user 0,03s system 99% cpu 0,469 total
Same problem happening on Windows, and with Pycharm
sam --version
returns
SAM CLI, version 0.46.2
I can build and invoke my lambda functions from the terminal inside PyCharm, just not from the Run interface. Updated awscli, samcli, nothing happened.
I suspect the problem started happening when I changed the Python venv to python3.7, but I can't see how those things relate
The next version (1.12) of the toolkit has improvements to the SAM executable handling.
You can try our EAP builds to see if it fixes the issue for you
Updated to 1.12 EAP, still having the same issue.
Fixed the issue by running where sam
in the terminal and switching the executable, not sure why I have two though
Describe the bug Update to latest EAP version and got this error everywhere.
Screenshots
Your Environment