genie exec resume rejects --approve-for-me and -C after the subcommand
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cli
- Domain
- cli
Research direction
Start by reading the genie exec and resume command definitions and the CLI argument parsing tests. Reproduce the reported ordering with --approve-for-me and -C, then check how options are declared for the parent command and subcommand. Done when both options work after resume, or the help output clearly explains their required position.
Written by the indexing model from the issue text.
Description
Release version
v0.3.0
What happened?
genie exec resume rejects the parent exec options when they come after the subcommand.
$ genie exec resume <session-id> --approve-for-me "noop"
error: unexpected argument '--approve-for-me' found
$ genie exec resume <session-id> -C /tmp "noop"
error: unexpected argument '-C' found
The same options work when placed before resume:
genie exec --approve-for-me -C <dir> --json resume <session-id> -
genie exec resume --help does not list --approve-for-me or -C, and it does not say that they must come before the subcommand. I found the working order by trial and error.
Expected: accept these options in either position, or document the required order in genie exec resume --help.
Steps to reproduce
- Run any
genie execsession and note its session ID. - Run
genie exec resume <session-id> --approve-for-me "noop". - The command fails with
unexpected argument. - Run
genie exec --approve-for-me resume <session-id> "noop". This form works.
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 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/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