Skip to content

Preview 3 a.k.a. 2.0.2 ships with PSReadLine 2.0.0 beta3, should be beta4 #1876

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

Closed
sba923 opened this issue Apr 13, 2019 · 11 comments
Closed

Comments

@sba923
Copy link

sba923 commented Apr 13, 2019

With beta3, we get #1570 back!

@TylerLeonhardt
Copy link
Member

@sba923 there is no official release of beta4 yet. Me sending you that build was for testing purposes. When a true release of beta4 comes out, it will be bundled with the extension.

@sba923
Copy link
Author

sba923 commented Apr 15, 2019

Sorry, I hadn't noticed that 'beta4' was a "leaked on the side" ;-) version.

Given the remaining issues on 'beta4', there's quite some remaining work on PSRL anyway if you ask me.

@sba923
Copy link
Author

sba923 commented May 24, 2019

@TylerLeonhardt Seems an official release of beta4 is being created... how are we going to get it to test with the VScode extension? As part of a new (official) preview of the extension? Maybe would be wise to ask a few people to test it before that?

@TylerLeonhardt
Copy link
Member

A release happening next week will have beta4 in it already. The Preview extention is our opportunity to "test in production" so we don't need another process for shipping builds

@sba923
Copy link
Author

sba923 commented May 24, 2019

Great! I must confess I'm a little confused about the relationship between preview releases of the VScode extension and beta releases of PSRL. The latter ought to be made available separately from the VScode extension 'cos PSRL is used in normal PS hosts as well...

@TylerLeonhardt
Copy link
Member

The PSRL addition in to the PowerShell extension is not quite stable enough to make its way into the Stable version of the extension.

That's why it's currently in Preview. It's been a substantial amount of work just to get it functional and even then, it's only functional on Windows as of right now.

Once we stablize the PSRL change, it will go into the Stable version of the extension and it will be the norm of the PowerShell extension.

@TylerLeonhardt
Copy link
Member

TylerLeonhardt commented May 24, 2019

Oh hmm you might be able to run:

Install-Module PSReadLine -AllowPrerelease

And the PowerShell extension should pick that new version up

@sba923
Copy link
Author

sba923 commented May 24, 2019

Here's what this gets me:

PS C:/WINDOWS/system32> Install-Module PSReadLine -AllowPrerelease -Verbose
VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.MetaProvider.PowerShell.dll
VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.CoreProviders.dll
VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.ArchiverProviders.dll
VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.NuGetProvider.dll
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='PSReadLine'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'PSReadLine'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.poshtestgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.poshtestgallery.com/api/v2/FindPackagesById()?id='PSReadLine'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'PSReadLine'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: Repository details, Name = 'OneGetTestSource', Location = 'https://www.poshtestgallery.com/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
WARNING: 'PSReadLine' matched module 'PSReadLine/2.0.0-beta4' from provider: 'PowerShellGet', repository 'PSGallery'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: Repository details, Name = 'OneGetTestSource', Location = 'https://www.poshtestgallery.com/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
WARNING: 'PSReadline' matched module 'PSReadline/2.0.0-beta2' from provider: 'PowerShellGet', repository 'OneGetTestSource'.
PackageManagement\Install-Package : Unable to install, multiple modules matched 'PSReadline'. Please specify a single -Repository.
At C:\program files\powershell\6\Modules\PowerShellGet\PSModule.psm1:9508 char:21
+ ...          $null = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidArgument: (Microsoft.PowerShel\u2026lets.InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : DisambiguateForInstall,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Where should I go from there?

@sba923
Copy link
Author

sba923 commented May 24, 2019

The PSRL addition in to the PowerShell extension is not quite stable enough to make its way into the Stable version of the extension.
That's why it's currently in Preview. It's been a substantial amount of work just to get it functional and even then, it's only functional on Windows as of right now.
Once we stablize the PSRL change, it will go into the Stable version of the extension and it will be the norm of the PowerShell extension.

My questioning was more about why there's (apparently) no stream of PSRL test releases outside of the consumption of PSRL by the VScode extension. But that's probably a topic I should address at lzybkr/PSReadline, not here ;-)

@rjmholt
Copy link
Contributor

rjmholt commented May 24, 2019

But that's probably a topic I should address at lzybkr/PSReadline

That's now at PowerShell/PSReadLine. I think the official release stream is the PowerShell Gallery (beta4 release).

It looks like in your case you want

Install-Module PSReadLine -Repository PSGallery -AllowPrerelease

@sba923
Copy link
Author

sba923 commented May 25, 2019

Thanks @rjmholt for the -Repository PSGallery tip.

I went for this, and then overwrote all copies of PSRL on my systems with the now-official beta4:

PS C:/WINDOWS/system32> Install-Module PSReadLine -Repository PSGallery -AllowPrerelease -Verbose -Force -Scope AllUsers                                                                                                                        VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.                                                                                            VERBOSE: Using the provider 'PowerShellGet' for searching packages.                                                     VERBOSE: Using the specified source names : 'PSGallery'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='PSReadLine'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'PSReadLine'.
VERBOSE: Performing the operation "Install-Module" on target "Version '2.0.0-beta4' of module 'PSReadLine'".
VERBOSE: The installation scope is specified to be 'AllUsers'.
VERBOSE: The specified module will be installed in 'C:\Program Files\PowerShell\Modules'.
VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
VERBOSE: Downloading module 'PSReadLine' with version '2.0.0-beta4' from the repository 'https://www.powershellgallery.com/api/v2/'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='PSReadLine'' for ''.
VERBOSE: InstallPackage' - name='PSReadLine', version='2.0.0-beta4',destination='C:\Users\steph\AppData\Local\Temp\758503296'
VERBOSE: DownloadPackage' - name='PSReadLine', version='2.0.0-beta4',destination='C:\Users\steph\AppData\Local\Temp\758503296\PSReadLine.2.0.0-beta4\PSReadLine.2.0.0-beta4.nupkg', uri='https://www.powershellgallery.com/api/v2/package/PSReadLine/2.0.0-beta4'
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/PSReadLine/2.0.0-beta4'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/PSReadLine/2.0.0-beta4'.
VERBOSE: Completed downloading 'PSReadLine'.
VERBOSE: InstallPackageLocal' - name='PSReadLine', version='2.0.0-beta4',destination='C:\Users\steph\AppData\Local\Temp\758503296'
VERBOSE: Validating the 'PSReadLine' module contents under 'C:\Users\steph\AppData\Local\Temp\758503296\PSReadLine.2.0.0-beta4' path.
VERBOSE: Test-ModuleManifest successfully validated the module manifest file 'C:\Users\steph\AppData\Local\Temp\758503296\PSReadLine.2.0.0-beta4'.
VERBOSE: Validating the authenticode signature and publisher of the catalog file or module manifest file of the module 'PSReadLine'.
VERBOSE: Found the catalog file 'PSReadLine.cat' in the module 'PSReadLine' contents.
VERBOSE: Valid authenticode signature found in the catalog file 'PSReadLine.cat' for the module 'PSReadLine'.
VERBOSE: Validating the 'PSReadLine' module files for catalog signing using the catalog file 'PSReadLine.cat'.
VERBOSE: The catalog signature in 'PSReadLine.cat' of the module 'PSReadLine' is valid and matches with the hash generated from the module contents.
VERBOSE: For publisher validation, current module 'PSReadLine' with version '2.0.0' with publisher name 'CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' from root certificate authority 'CN=Microsoft Root Certificate Authority 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US'. Is this module signed by Microsoft: 'True'.
VERBOSE: For publisher validation, using the previously-installed module 'PSReadLine' with version '2.0.0' under 'C:\Users\steph\OneDrive\Documents\PowerShell\Modules\PSReadLine\2.0.0' with publisher name 'CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' from root certificate authority 'CN=Microsoft Root Certificate Authority 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US'. Is this module signed by Microsoft: 'True'.
VERBOSE: Authenticode issuer 'CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' of the new module 'PSReadLine' with version '2.0.0' matches with the authenticode issuer 'CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' of the previously-installed module 'PSReadLine' with version '2.0.0'.
VERBOSE: Checking for possible command collisions for the module 'PSReadLine' commands.
VERBOSE: Module 'PSReadLine' was installed successfully to path 'C:\Program Files\PowerShell\Modules\PSReadLine\2.0.0'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants