Bootstrap: the last two steps run as the user who owns the install
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Read the bootstrap script and locate run_doctor, build_asa_steering_vector, and run_as_target; the issue does not name the script path. Check the test that reads the script and the install job “bootstrap via sudo for a regular user.” Done means both steps run through run_as_target, the test confirms every checkout-code step does, and the job finds no checkout files the user does not own.
Written by the indexing model from the issue text.
Description
What needs doing
run_doctor and the check of an existing steering vector in
build_asa_steering_vector run as the user the script runs as. With
sudo bash that is root. Run both through run_as_target, as the
clone, the CLI install, the model download and the TUI build are.
Why
Root then runs code from a folder that the user owns, and can leave
files there that the user cannot change. After sudo bash the
atlas command may also not be on root's path; then the vector check
cannot pass and the vector is built again.
Done when
- A test reads the script: every step that runs code from the
checkout goes throughrun_as_target. - The install job "bootstrap via sudo for a regular user" finds
no file in the checkout that the user does not own.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 197
- Avg merge
- 5h 19m
- Merged PRs (30d)
- 76
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 inferstep/ATLAS
-
area/install documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/install reliability status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/cli
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area/proxy reliability status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
area/ci documentation status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramnes/notion-sdk-py#409 ·
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lindicaphxag-tech/kaggle#28 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
BSData/horus-heresy-3rd-edition#3211 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day