-
Notifications
You must be signed in to change notification settings - Fork 909
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
Chocolatey fails to load all PowerShell helper cmdlets when attempting to loads modules #2412
Comments
/cc @mkevenaar |
7 tasks
AdmiringWorm
added a commit
to AdmiringWorm/choco
that referenced
this issue
Oct 21, 2021
…rning This commit updates the chocoalteyInstaller module to not output an error when failing to load the Chocolatey Licensed Extension which would prevent all helper cmdlets in FOSS being exported. Instead the importing have been wrapped inside a try/catch block and writes out a Warning that includes the reason the importing failed.
gep13
pushed a commit
to AdmiringWorm/choco
that referenced
this issue
Oct 21, 2021
…rning This commit updates the chocoalteyInstaller module to not output an error when failing to load the Chocolatey Licensed Extension which would prevent all helper cmdlets in FOSS being exported. Instead the importing have been wrapped inside a try/catch block and writes out a Warning that includes the reason the importing failed.
gep13
pushed a commit
to AdmiringWorm/choco
that referenced
this issue
Oct 21, 2021
This commit updates the chocolateyInstaller module to not output an error when failing to load the Chocolatey Licensed Extension which would prevent all helper cmdlets in FOSS being exported. Instead the importing have been wrapped inside a try/catch block and writes out a Warning that includes the reason the importing failed.
gep13
added a commit
that referenced
this issue
Oct 21, 2021
…lper-cmdlets-when-extensions-fails-to-load (#2412) Change importing of Licensed extension to output warning
gep13
added a commit
that referenced
this issue
Oct 27, 2021
* hotfix/0.11.3: (version) 0.11.3-beta (maint) Prevent inclusion of snk file (#2336) Remove quotes from InstallLocation (#877) Set SourceType for packages parsed from config (#2289) Add acknowledgements and license files (#2289) Update Rhino.Licensing dependency (maint) Replace unversioned Rhino.Licensing dll (#2398) Restore PowerShell v2 support (#2412) Switch to output warning on failure
gep13
added a commit
that referenced
this issue
Oct 27, 2021
* master: (version) 0.11.3 (version) 0.11.3-beta (maint) Prevent inclusion of snk file (#2336) Remove quotes from InstallLocation (#877) Set SourceType for packages parsed from config (#2289) Add acknowledgements and license files (#2289) Update Rhino.Licensing dependency (maint) Replace unversioned Rhino.Licensing dll (#2398) Restore PowerShell v2 support (#2412) Switch to output warning on failure # Conflicts: # .uppercut
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What You Are Seeing?
When the Chocolatey Licensed extension fails to load some of the expected helper cmdlets won't be available due to the importing being aborted before everything is processed.
This also affects when normal extensions are imported if they fail to be imported in some way.
This especially affects users of the AU extension which makes a monkey patch of the cmdlets to make maintenance easier for the user, in which case the Licensed extension can not be loaded.
What is Expected?
All cmdlets available in open source Chocolatey should be loaded even in the case where an extension is failing to load, even if that extension is the Licensed edition of Chocolatey.
Before Chocolatey 0.11.0 failing to import any extension with a DLL extension would report a Warning, but continue execution. After 0.11.1 this has been changed to an error, and is preventing the execution of the module loading.
How Did You Get This To Happen? (Steps to Reproduce)
Get-ChocolateyWebFile
cmdlet.Remove-Item $env:TEMP\chocolatey\au
Output Log
Chocolatey Log
No log file available
AU Log
Console:
Log File:
Manual Import
The text was updated successfully, but these errors were encountered: