You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using expand.FuncEnviron to generate runner and using this runner to run the file type Node that contains any pipe operator symbol, it will cause environment variables to not transfer across pipes and be visible for all command statements.
That's because expand.FuncEnviron does implement the Environ interface, but the Each is no-op method, so when executing runner.Subshell() to get a new runner for one side command of pipe, environment variables will not be copied as expected.
It would be helpful to add comments to the expand.FuncEnviron function. This will prevent others from troubleshooting similar problems for a long time, like I did.
The text was updated successfully, but these errors were encountered:
When using
expand.FuncEnviron
to generate runner and using this runner to run thefile
type Node that contains any pipe operator symbol, it will cause environment variables to not transfer across pipes and be visible for all command statements.That's because
expand.FuncEnviron
does implement theEnviron
interface, but theEach
is no-op method, so when executingrunner.Subshell()
to get a new runner for one side command of pipe, environment variables will not be copied as expected.It would be helpful to add comments to the expand.FuncEnviron function. This will prevent others from troubleshooting similar problems for a long time, like I did.
The text was updated successfully, but these errors were encountered: