cwd target doesn't work with ibazel
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- shell
- Domain
- build-system, tooling
Research direction
Start with the README section “Running tools in the current working directory” and reproduce the issue using ./tools/ibazel with a server target, then interrupt it with SIGINT. Compare that behavior with the shell script shown in the issue and the linked aspect-workflows-template change. Done means deciding and documenting whether rules_multitool should address the zombie process behavior or leave it to bazel run.
Written by the indexing model from the issue text.
Description
A customer pointed out that the pattern documented on the README
https://github.com/theoremlp/rules_multitool?tab=readme-ov-file#running-tools-in-the-current-working-directory
doesn't work correctly with some programs like ibazel (bazel-watcher) because zombie processes get left behind.
We think this post from @lberki is related https://groups.google.com/g/bazel-discuss/c/I6TWUv8AI5o
I think this can be reproduced by running some server target under ./tools/ibazel //my/server:target, then when you ctrl-c (SIGINT) you'll still see the server is running.
So we changed our aspect init https://github.com/aspect-build/aspect-workflows-template/pull/87
to still stamp out a script that DOES function correctly:
#!/bin/sh
target="@multitool//tools/$(basename "$0")"
bazel 2>/dev/null build "$target" && exec $(bazel info execution_root)/$(bazel 2>/dev/null cquery --output=files "$target") "$@"
Personally I think bazel run is still just busted in a way rules_multitool shouldn't try to fix.
- Dominant language
- Starlark
- Stars
- 26
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bazel-contrib/rules_multitool
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
bazel-contrib/rules_multitool#131 ·
-
make a new releaseOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bazel-contrib/rules_multitool#130 · 2 comments · 3 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
bazel-contrib/rules_multitool#127 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
bazel-contrib/rules_multitool#113 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bazel-contrib/rules_multitool#107 · 1 comment ·
All issues in bazel-contrib/rules_multitool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-telemetry/opentelemetry-go-compile-instrumentation#1512 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nasa/fprime#6225 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bioconda/bioconda-recipes#70401 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vitest-dev/vitest#11633 · 1 comment ·
Maintainers usually reply within 1 day