[Bug] install.ps1 fails via ssh/headless, windows server 2022, ansible

Open
#82 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
powershell
Domain
cli

Research direction

Start in install.ps1 at the Write-InstallInfo function and the Install-Scoop call around line 555. Reproduce the failure with PowerShell 5.1 on Windows Server 2022 through SSH or a headless session, then verify installation completes without the ForegroundColor exception and that normal terminal output still works.

Written by the indexing model from the issue text.

Description

bug

Bug Report

Current Behavior

Install script fails due to color arguments in the script.

Error message:

{
  "changed": true,
  "debug": [],
  "error": [
    {
      "category_info": {
        "activity": "Write-InstallInfo",
        "category": "InvalidData",
        "category_id": 6,
        "reason": "ParentContainsErrorRecordException",
        "target_name": "",
        "target_type": ""
      },
      "error_details": null,
      "exception": {
        "help_link": null,
        "hresult": -2146233087,
        "inner_exception": null,
        "message": "Cannot process argument transformation on parameter 'ForegroundColor'. Cannot convert null to type \"System.ConsoleColor\" due to enumeration values that are not valid. Specify one of the following enumeration values and try again. The possible enumeration values are \"Black,DarkBlue,DarkGreen,DarkCyan,DarkRed,DarkMagenta,DarkYellow,Gray,DarkGray,Blue,Green,Cyan,Red,Magenta,Yellow,White\".",
        "source": null,
        "type": "System.Management.Automation.ParentContainsErrorRecordException"
      },
      "fully_qualified_error_id": "ParameterArgumentTransformationError,Write-InstallInfo",
      "output": "Write-InstallInfo : Cannot process argument transformation on parameter 'ForegroundColor'. Cannot convert null to type \r\n\"System.ConsoleColor\" due to enumeration values that are not valid. Specify one of the following enumeration values and \r\ntry again. The possible enumeration values are \"Black,DarkBlue,DarkGreen,DarkCyan,DarkRed,DarkMagenta,DarkYellow,Gray,Da\r\nrkGray,Blue,Green,Cyan,Red,Magenta,Yellow,White\".\r\nAt C:\\downloads\\scoop\\install.ps1:555 char:5\r\n+     Write-InstallInfo (\"Initializing...\")\r\n+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          : InvalidData: (:) [Write-InstallInfo], ParentContainsErrorRecordException\r\n    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Write-InstallInfo\r\n \r\n",
      
      "pipeline_iteration_info": [],
      "script_stack_trace": "at Install-Scoop, C:\\downloads\\scoop\\install.ps1: line 555\r\nat <ScriptBlock>, C:\\downloads\\scoop\\install.ps1: line 694\r\nat <ScriptBlock>, <No file>: line 2",
      "target_object": null
    }
  ],
  "host_err": "",
  "host_out": "",
  "information": [],
  "output": [],
  "result": {},
  "verbose": [],
  "warning": []
}
Expected Behavior

Not to throw this exception.

Additional context/output
Possible Solution

I worked around this by removing the terminal color code in the Write-InstallInfo function of the install script.

System details

Windows version: Server 2022

OS architecture: 64bit

PowerShell version: 5.1

Dominant language
PowerShell
Stars
1.3k
Forks
155
Avg merge
5h 24m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ScoopInstaller/Install

All issues in ScoopInstaller/Install

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.