main: silent extension activation failure
See original GitHub issue- Extension fails to start but no error is showed to the user.
- Document language appears to be
Ansible
and syntax highlighting works, only adding more to the confusion - There is no Ansible output channel, indication of crash
- Extensio host output channel contains the unpleasant details:
[2022-03-02 09:54:39.821] [exthost] [error] Activating extension redhat.ansible failed due to an error:
[2022-03-02 09:54:39.822] [exthost] [error] Error: Cannot find module './features/vault'
Require stack:
- c:\Users\sorin\.vscode\extensions\redhat.ansible-0.7.1\out\client\src\extension.js
- c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js
- c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js
- c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:934:15)
at Module._load (internal/modules/cjs/loader.js:779:27)
at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
at Function.i._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:112:32271)
at Function.p._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:112:28855)
at Function.v._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:107:60382)
at Module.require (internal/modules/cjs/loader.js:1006:19)
at h (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:4:699)
at Object.<anonymous> (c:\Users\sorin\.vscode\extensions\redhat.ansible-0.7.1\out\client\src\extension.js:26:17)
at Module.u._compile (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:4:1313)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1155:10)
at Module.load (internal/modules/cjs/loader.js:982:32)
at Module._load (internal/modules/cjs/loader.js:823:14)
at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
at Function.i._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:112:32271)
at Function.p._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:112:28855)
at Function.v._load (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:107:60382)
at Module.require (internal/modules/cjs/loader.js:1006:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Function.r [as __$__nodeRequire] (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:5:101)
at w._loadCommonJSModule (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:112:30425)
at w._doActivateExtension (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:98:13341)
at w._activateExtension (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:98:12293)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)
at w.$activate (c:\Users\sorin\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:98:21810)
Update: apparently vsix archive contains only extension.js file and missing the other nearby js files.
Not sure when this happened but it does highlight a fatal flaws in our testing.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Managing Extensions in Visual Studio Code
Manage extensions. VS Code makes it easy to manage your extensions. You can install, disable, update, and uninstall extensions through the Extensions view,...
Read more >How to fix Jupyter extension activation failed when opening ...
In my case, upgrading to the pre-release version of the Jupyter extension (v2022.5.1001281006) solved it right away.
Read more >ActivateDoc2 Method (ISldWorks) - 2012 - SolidWorks Web Help
Parameters. Name: Name of document to activate; Silent: True if dialogs and warning messages should be avoided, false if dialogs and warning
Read more >Troubleshoot on-premises deployments | Dynamics 365
This article provides troubleshooting information for deployments of Microsoft Dynamics 365 Finance + Operations (on-premises).
Read more >Installing a Windows Agent/Probe silently fails to ... - N-able
Troubleshooting > Installing a Windows Agent/Probe silently fails to complete, due to "Server rejected activation information".
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
Please install
0.11.11
, i fixed the bad release. Now I also working on introducing some preventive measures for avoiding the same accident from happening again. That is the 2nd time it happens, the first time was back in March.Funny aspect is that the artifact from GHA was good, only the one produced by Jenkins was buggy. The plan is to change Jenkins pipeline to just publish GHA artifact and avoid building it again.
A secondary goal is to make a pre-release every day, if during that day there was a change merged on main branch.
Also stumbled onto this issue with v0.11.10, on Win11 / WSL2 after wondering why my Ansible syntax highlighting had suddenly stopped working. Downgrading to the previous v0.10.0 got it working again.