[bazel.build] Problem with /rules/lib/builtins/ctx
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 72
Description
### Page link:
https://bazel.build/rules/lib/builtins/ctx
### Problem description (include actual vs expected text, if applicable):
Unable to leave feedback on documentation. Whenever I click the leave feedback button the screen freezes. I am using Safari 18.6 (20621.3.11.11.3).
### Where do you see this issue? (include link to specific section of the page, if applicable)
When I click 'SEND FEEDBACK' on this page:
https://bazel.build/rules/lib/builtins/ctx#bin_dir
### Any other information you'd like to share?
Bazel documentation is woefully inadequate because it does not explain the exact execution environment of the rules, and the system. For example, what is the current working directory of a rule? How does bazel pick the path to declared files? When executing, how does it pick the path for the sandbox, etc... This is all glossed over in the "tutorial" and the reader is then sent off to "RTFS". By contrast, when executing a shell script, or a Makefile, you understand exactly what the environment is, where the make process is executing exactly, and what the configuration of the execution environment for your rules are. Without this information it's infuriating to debug even trivial rules until you learn it all through experimentation and reverse engineering, but you have no guarantees which of this information will be stable from release to release, and which can change.
Contributor guide
Research direction
Open the feedback control on https://bazel.build/rules/lib/builtins/ctx#bin_dir in Safari 18.6 and reproduce the screen freeze when selecting “SEND FEEDBACK.” Done means feedback can be submitted without the page freezing; the broader requests about rule execution environments are separate documentation gaps and need narrower scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100