CLI option for override steep command at spawn worker #511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think to execute Steep with Bazel and rules_ruby.
So, I writen Bazel configuration as follows.
But,
bazel test
is failed.Bazel is execute
main
wrapped by Ruby script instead of directlymain
executed.And, Bazel is not set path of
main
to PATH environment variable in sandbox.Therefore, Steep cannot spawn worker using
Open3.popen2("steep", ...)
.To solve this issue, add
--steep-command
option for specify command to spawn worker.Rewrite Bazel configuration above using
--steep-command
option as follows then I could execute Steep with Bazel.I think that need
--steep-command
option to execute Steep with Bazel.But, I have not idea other use-case...