--sandbox and --approve-for-me cannot be combined, and the help text implies they can
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by reading the genie exec --help option definition and the argument validation that rejects --sandbox with --approve-for-me; the payload does not name their files. Confirm the current help text and reproduce with the command in the issue. Done when the help explains that --approve-for-me sets the workspace-write sandbox and cannot be combined with -s or --sandbox, or the stated combination is accepted.
Written by the indexing model from the issue text.
Description
Release version
v0.3.0
What happened?
--sandbox and --approve-for-me cannot be used together, but the help text suggests they fit together.
$ genie exec -s workspace-write --approve-for-me "noop"
error: the argument '--sandbox <SANDBOX_MODE>' cannot be used with '--approve-for-me'
The help text for --approve-for-me says:
Route approval requests through automatic review using the workspace-write sandbox
A reader takes this to mean you should pair it with -s workspace-write, which then fails.
Expected: the help text for --approve-for-me says that it sets the workspace-write sandbox itself and cannot be combined with -s or --sandbox. Accepting -s workspace-write as a no-op would also work.
Steps to reproduce
- Run
genie exec -s workspace-write --approve-for-me "noop". - The command exits with the error above.
- Run
genie exec --helpand read the--approve-for-meentry.
Environment
macOS (Apple silicon), Genie Code CLI installed with install.sh.
- Dominant language
- No language data
- Stars
- 13
- Forks
- 1
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 databricks/genie-code-cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
All issues in databricks/genie-code-cli
Similar issues
-
found in release: 3.50 has reproducible steps team-tool tool
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
flutter/flutter#196430 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned sessionPossibly taken @bodapatisaikrishna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
datafusion-contrib/StreamFusion#653 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day