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
I tried this for other ENV var that i needed and this does not work. parseRunner splits by spaces so the ENV var becomes a file that spawn tries to call
Rather than improving the support for runner string, I think something like this would be most appropriate for the internal usage of spawn.
NOTE: When supplying options.env to spawn it will override the default of passing process.env, so this must be explicitly provided by config. This additionally provides the option of passing {} to prevent this default behaviour.
The text was updated successfully, but these errors were encountered:
I got a different issue (I think ruby hangs with spring enabled while compiling)
"fixed" by disabling spring in bin/rails but not really a good change
So +1 for this proposal
Maybe I will open a PR for making this change later
Reported by @dreyks here.
Rather than improving the support for
runner
string, I think something like this would be most appropriate for the internal usage ofspawn
.NOTE: When supplying
options.env
tospawn
it will override the default of passingprocess.env
, so this must be explicitly provided by config. This additionally provides the option of passing{}
to prevent this default behaviour.The text was updated successfully, but these errors were encountered: