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

aio rt:activation:list does NOT work in Windows 10 #102

Closed
visaq opened this issue Jan 31, 2020 · 2 comments
Closed

aio rt:activation:list does NOT work in Windows 10 #102

visaq opened this issue Jan 31, 2020 · 2 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@visaq
Copy link

visaq commented Jan 31, 2020

After deploying app into IO, I ran "aio app run" in command prompt and then using the url under web-src/src/config.json, I invoked my app. Then I entered "aio rt:activation:list" in Terminal tab of VS code and I got the below error. I got the same error when I repeated these same steps with "aio app run --local". However, "wsk activation list" gave me the list of activation ids.
"aio rt:activation:list
aio : File C:\Users\mallicha\AppData\Roaming\npm\aio.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1

  • aio rt:activation:list
    • CategoryInfo : SecurityError: (:) [], PSSecurityException
    • FullyQualifiedErrorId : UnauthorizedAccess"

OS: Windows 10 Enterprise
Browse: Google Chrome - Version 79.0.3945.130 (Official Build) (64-bit)
aio --version --> @adobe/aio-cli/3.0.0 win32-x64 node-v12.13.1

Issue-ActicationList

@meryllblanchet meryllblanchet added bug Something isn't working help wanted Extra attention is needed labels Feb 5, 2020
@DrewML
Copy link
Contributor

DrewML commented Feb 6, 2020

Hey @visaq,

Unfortunately this is a recent behavior change in npm which will cause this problem for any globally installed packages on Windows:

npm/cli#470

Some work-arounds are offered in that thread

@meryllblanchet
Copy link

Closing the issue as this related to npm/cli#470

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants