Skip to content

Extension won't start with alpha 18 on CentOS #662

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.

Sign up for GitHub

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

Jump to bottom
Closed
bgelens opened this issue Apr 7, 2017 · 2 comments
Closed

Extension won't start with alpha 18 on CentOS #662

bgelens opened this issue Apr 7, 2017 · 2 comments
Labels
Area-Extension Terminal Issue-Bug A bug to squash. OS-Linux
Milestone
0.12.2

Comments

@bgelens
Copy link

bgelens commented Apr 7, 2017

System Details

  • Operating system name and version: CentOS 7.3 x64
  • VS Code version: 1.11.1
  • PowerShell extension version: 0.12.1
  • Output from $PSVersionTable:
Name                           Value                                           
----                           -----                                           
PSVersion                      6.0.0-alpha                                     
PSEdition                      Core                                            
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                         
BuildVersion                   3.0.0.0                                         
GitCommitId                    v6.0.0-alpha.18                                 
CLRVersion                                                                     
WSManStackVersion              3.0                                             
PSRemotingProtocolVersion      2.3                                             
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with the extension not being started since PowerShell alpha 18 installation.
2799bb4b-0edb-4cc3-bccb-4db618018214

Attached Logs

logs.zip
@daviwil
Copy link
Contributor

daviwil commented Apr 7, 2017

Not sure what the deal is with that module failure, I'll check it out as soon as I spin up a Linux VM.

@daviwil daviwil added this to the April 2017 milestone Apr 7, 2017
@daviwil
Copy link
Contributor

daviwil commented Apr 7, 2017

Apparently the new change to PSModulePath casing caused it! Just need to change the startup script.

daviwil added a commit to daviwil/vscode-powershell that referenced this issue Apr 7, 2017
@daviwil
Fix extension startup on Linux/macOS with PS 6 Alpha 18
1fbd1c1 
This change fixes an issue caused by PowerShell 6 Alpha 18 where the
PSModulePath casing on UNIX systems has been changed from PSMODULEPATH
back to PSModulePath.  This change broke the startup script that
manipulates the PSModulePath so the extension fails to load in the new
version.

This is a breaking change for those using a previous version of
PowerShell 6 on UNIX systems.

Fixes PowerShell#662.
@daviwil daviwil mentioned this issue Apr 7, 2017
Merged
@daviwil daviwil modified the milestones: April 2017, 0.12.2 Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Extension Terminal Issue-Bug A bug to squash. OS-Linux
Projects
None yet
Milestone
0.12.2
Development

No branches or pull requests
2 participants
@daviwil @bgelens