kakkun61/ghcman

Update-GhcmanVersionFile : 404 Not Found

yokodake opened this issue · 5 comments

Describe the bug

When invoking Update-GhcmanVersionFile the following error is raised:

PS C:\> Update-GhcmanVersionFile
Invoke-WebRequest: 404: Not Found

I don't know much about PS but i think the [Version] "attribute" when setting the $ghcmanVersion is at fault here:

PS C:\> Set-Variable ghcmanVersion -Option Constant -Value [Version]"4.8"
PS C:\> $ghcmanVersion
[Version]4.8
PS C:\> Write-Output "https://raw.githubusercontent.com/kakkun61/ghcman/master/version.$ghcmanVersion.yaml"
https://raw.githubusercontent.com/kakkun61/ghcman/master/version.[Version]4.8.yaml
PS C:\> Invoke-WebRequest "https://raw.githubusercontent.com/kakkun61/ghcman/master/version.$ghcmanVersion.yaml"
Invoke-WebRequest: 404: Not Found

PS C:\>  Set-Variable ghcmanVersion -Option Constant -Value "4.8"
PS C:\> $ghcmanVersion
4.8
PS C:\> Invoke-WebRequest "https://raw.githubusercontent.com/kakkun61/ghcman/master/version.$ghcmanVersion.yaml"

StatusCode        : 200
StatusDescription : OK
Content           : ...

To Reproduce

Steps to reproduce the behavior:

Following the Readme:

  1. Run Cmdlet Import-Module ghcman
  2. Run Cmdlet Get-Module ghcman
  3. Run Cmdlet Update-GhcmanVersionFile
  4. See error 'Invoke-WebRequest: 404: Not Found`

Expected behavior

The cmdlet invocation to succeed and the versionfile to be updated.

Environment

  • OS: [e.g. Windows 10 19044]
  • PowerShell:
Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
  • Version: 4.8

Thank you for your report. I'll check this later.

Please reopen this issue if it happens again.

I found that this issue was still occurred. Hmm, my local development package does not occur this.

Fixed.