Skip to content

Conversation

@cderv
Copy link
Collaborator

@cderv cderv commented Dec 12, 2025

When Scoop fails to download or install Quarto (e.g., 503 server errors), the action would still report "Quarto Installed !" and succeed.

The PowerShell script had no error handling and the bash wrapper didn't check exit codes, causing installation failures to be silently ignored.

This PR fixes that

cderv added 10 commits December 11, 2025 21:06
When Scoop fails to download or install Quarto (e.g., 503 server errors),
the action would still report "Quarto Installed !" and succeed.

The PowerShell script had no error handling and the bash wrapper didn't
check exit codes, causing installation failures to be silently ignored.
The PowerShell script already verifies Quarto is available with
Get-Command. The bash check was redundant and failing because
GITHUB_PATH updates only take effect in subsequent steps, not
within the same step where the PATH is modified.
The Get-Command verification was failing because $GITHUB_PATH only
affects future steps, not the current PowerShell session. Now we
also update $env:PATH so the verification can find quarto.
Previously each OS had different verification approaches:
- Windows: PowerShell Get-Command check (failed due to PATH timing)
- Linux/macOS: No verification

Now all platforms use a single bash verification step that runs
after installation. This works because GITHUB_PATH updates take
effect in subsequent steps, not within the same step.
Scoop commands leave $LASTEXITCODE in unpredictable states even on
success. With $ErrorActionPreference = "Stop", real errors will be
caught automatically. The separate bash verification step confirms
installation succeeded.
@cderv cderv merged commit 10ecffe into main Dec 12, 2025
15 checks passed
@cderv cderv deleted the fix-windows-error-handling branch December 12, 2025 13:00
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

Successfully merging this pull request may close these issues.

2 participants