Remove use of pipefail, switch to use CustomExecution, add decoration for unset settings

[SanjulaGanepola]

Changes

• "Cannot bind parameter 'Option'" When running workflow #78
  • Tested on Windows
• Switch to use CustomExecution for VS Code task to avoid use of pipefail but still be able to retrieve execution output
• Add decoration for settings which are not assigned a value but are selected. Supporting interactive user input for secrets and variables were causing issues where the child process was being terminated on input request. This PR removes support for interactive input in favour of using the UI (this can be reverted if the issue is addressed)

[SanjulaGanepola]

Note: This was added due to nodejs/node#7367 (comment)

[ChristopherHX]

Hmm...

This error is new for me, the change with only removed images worked somehow

Got a try on macOS today, seems there is a new bug included here.

 *  Executing task: GitHub Local Actions: Help/test #6 

/Users/USER/Downloads/act_Darwin_arm64/act --workflows ".github/workflows/main.yml" --job "test" --secret-file "" --var-file "" --input-file "" --platform self-hosted=-self-hosted --eventpath ""

time="2024-11-26T20:25:04+01:00" level=fatal msg="$HOME is not defined"

Task exited with exit code 1.

 *  The terminal process failed to launch (exit code: 1). 

branching via process.env == 'win32' is the safest in short term

[ChristopherHX]

I wonder if this stuff can be tested on CI?

the -P macos-latest=-self-hosted -P windows-latest=-self-hosted toggle don't require docker

Myself didn't go so far to test my vscode extensions, but something very useful.

[ChristopherHX]

maybe env: [...process.env, ...settings.secrets(the rest)]

So HOME is never undefined

[SanjulaGanepola]

I wonder if this stuff can be tested on CI?

the -P macos-latest=-self-hosted -P windows-latest=-self-hosted toggle don't require docker

Myself didn't go so far to test my vscode extensions, but something very useful.

Interesting idea. I have some ideas for vscode testing which I have done previously. We can have a look at setting up a test framework once these bugs are resolved.

@ChristopherHX Could you have another try with this PR? I have pushed some more updates and confirmed it worked on Windows and Linux. I am unable to test on MacOS.

[SanjulaGanepola]

@ChristopherHX PR #70 in fact actually builds on top of this one to address some other issues as well so it might be easier to just test with that branch.

[ChristopherHX]

pr #70 works fine so far